- 24 Jul, 2018 1 commit
-
-
Oran Agra authored
it looks like on slow machines we're getting: [err]: slave buffer are counted correctly in tests/unit/maxmemory.tcl Expected condition '$slave_buf > 2*1024*1024' to be true (16914 > 2*1024*1024) this is a result of the slave waking up too early and eating the slave buffer before the traffic and the test ends.
-
- 23 Jul, 2018 6 commits
-
-
antirez authored
-
antirez authored
Related to #5157. The PR author correctly indentified that the check was duplicated, but removing the second one introduces a bug that was fixed in the past (hence the duplication). Instead we can remove the first instance of the check without issues.
-
antirez authored
-
Salvatore Sanfilippo authored
fix recursion typo in zmalloc_usable
-
antirez authored
Related to #4883.
-
Salvatore Sanfilippo authored
Adds memory information about the scripts' cache to INFO
-
- 22 Jul, 2018 2 commits
-
-
Itamar Haber authored
-
Oran Agra authored
-
- 20 Jul, 2018 2 commits
- 19 Jul, 2018 9 commits
-
-
antirez authored
They are actually delayed a few seconds, so let's call them "recent".
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Related to #4727.
-
Salvatore Sanfilippo authored
move getClientsMaxBuffers func into info clients command
-
- 18 Jul, 2018 5 commits
-
-
antirez authored
-
antirez authored
See #5135 for more context.
-
antirez authored
See #5135 for some context.
-
Salvatore Sanfilippo authored
make active defrag test more stable
-
Oran Agra authored
on slower machines, the active defrag test tended to fail. although the fragmentation ratio was below the treshold, the defragger was still in the middle of a scan cycle. this commit changes: - the defragger uses the current fragmentation state, rather than the cache one that is updated by server cron every 100ms. this actually fixes a bug of starting one excess scan cycle - the test lets the defragger use more CPU cycles, in hope that the defrag will be faster, but also give it more time before we give up.
-
- 17 Jul, 2018 11 commits
-
-
Salvatore Sanfilippo authored
Accept write commands if persisting is disabled
-
Salvatore Sanfilippo authored
Update the comment
-
antirez authored
-
Salvatore Sanfilippo authored
Fix xreadgroup with '$' ID.
-
antirez authored
Related to #5135, see discussion there.
-
Salvatore Sanfilippo authored
fix rare replication stream corruption with disk-based replication
-
dejun.xdj authored
It's already checked if xreadgroup is set and groupname is NULL.
-
dejun.xdj authored
Redis will always return an empty result when '$' ID is specified with xreadgroup command, it's meaningless.
-
Oran Agra authored
The slave sends \n keepalive messages to the master while parsing the rdb, and later sends REPLCONF ACK once a second. rarely, the master recives both a linefeed char and a REPLCONF in the same read, \n*3\r\n$8\r\nREPLCONF\r\n... and it tries to trim two chars (\r\n) from the query buffer, trimming the '*' from *3\r\n$8\r\nREPLCONF\r\n... then the master tries to process a command starting with '3' and replies to the slave a bunch of -ERR and one +OK. although the slave silently ignores these (prints a log message), this corrupts the replication offset at the slave since the slave increases the replication offset, and the master did not. other than the fix in processInlineBuffer, i did several other improvments while hunting this very rare bug. - when redis replies with "unknown command" it includes a portion of the arguments, not just the command name. so it would be easier to understand what was recived, in my case, on the slave side, it was -ERR, but the "arguments" were the interesting part (containing info on the error). - about a year ago i added code in addReplyErrorLength to print the error to the log in case of a reply to master (since this string isn't actually trasmitted to the master), now changed that block to print a similar log message to indicate an error being sent from the master to the slave. note that the slave is marked as CLIENT_SLAVE only after PSYNC was received, so this will not cause any harm for REPLCONF, and will only indicate problems that are gonna corrupt the replication stream anyway. - two places were c->reply was emptied, and i wanted to reset sentlen this is a precaution (i did not actually see such a problem), since a non-zero sentlen will cause corruption to be transmitted on the socket.
-
antirez authored
-
Salvatore Sanfilippo authored
remove ineffective loop in dictGetSomeKeys.
-
- 16 Jul, 2018 4 commits
-
-
Salvatore Sanfilippo authored
Streams: using streamCompareID() instead of direct compare.
-
Salvatore Sanfilippo authored
bugfix in sdsReqType creating 64bit sds headers on 32bit systems
-
antirez authored
Reading the PR gave me the opportunity to better specify what the code was doing in places where I was not immediately sure about what was going on. Moreover I documented the structure in server.h so that people reading the header file will immediately understand what the structure is useful for.
-
Salvatore Sanfilippo authored
slave buffers were wasteful and incorrectly counted causing eviction
-