- 23 Jun, 2016 2 commits
-
-
antirez authored
It's more natural to call the last entry added as "last", the original commet got me confused until I actually read the code.
-
antirez authored
Most of the time to check the last element is the way to go, however there are patterns where the contrary is the best choice. Zig-zag scanning implemented in this commmit always checks the obvious element first (the last added -- think at a loop where the last element allocated gets freed again and again), and continues checking one element in the head and one in the tail. Thanks to @dvisrky that fixed the original implementation of the function and proposed zig zag scanning.
-
- 22 Jun, 2016 1 commit
-
-
antirez authored
-
- 16 Jun, 2016 4 commits
-
-
antirez authored
This bug most experienced effect was an inability of Redis to reconfigure back old masters to slaves after they are reachable again after a failover. This was due to failing to reset the count of the pending commands properly, so the master appeared fovever down. Was introduced in Redis 3.2 new Sentinel connection sharing feature which is a lot more complex than the 3.0 code, but more scalable. Many thanks to people reporting the issue, and especially to @sskorgal for investigating the issue in depth. Hopefully closes #3285.
-
antirez authored
I recently introduced populating the autocomplete help array with the COMMAND command if available. However this was performed before parsing the arguments, defaulting to instance 6379. After the connection is performed it remains stable. The effect is that if there is an instance running on port 6339, whatever port you specify is ignored and 6379 is connected to instead. The right port will be selected only after a reconnection. Close #3314.
-
antirez authored
Reference issue #3218. Checking the code I can't find a reason why the original RESTORE code was so opinionated about restoring only the current version. The code in to `rdb.c` appears to be capable as always to restore data from older versions of Redis, and the only places where it is needed the current version in order to correctly restore data, is while loading the opcodes, not the values itself as it happens in the case of RESTORE. For the above reasons, this commit enables RESTORE to accept older versions of values payloads.
-
antirez authored
Comment format fixed + local var modified from camel case to underscore separators as Redis code base normally does (camel case is mostly used for global symbols like structure names, function names, global vars, ...).
-
- 15 Jun, 2016 2 commits
- 14 Jun, 2016 3 commits
-
-
zach shipko authored
-
antirez authored
-
antirez authored
-
- 13 Jun, 2016 6 commits
-
-
antirez authored
Related to #3293.
-
antirez authored
Related to #3293.
-
antirez authored
We need to be free to shuffle fields or add more fields in a structure without breaking code. Related to issue #3293.
-
antirez authored
Now that modules receive RedisModuleString objects on loading, they are allowed to call the String API, so the context must be released correctly. Related to #3293.
-
antirez authored
Related to PR #3293.
-
antirez authored
-
- 10 Jun, 2016 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
All lists are now represented via quicklists. Quicklists are never represented referencing robj structures, so trying to compress their representation does not make sense. That the new way is faster was experimentally verified with micro benchmarks in order to prove that the intuition was correct.
-
andyli authored
-
antirez authored
-
- 08 Jun, 2016 1 commit
-
-
antirez authored
-
- 07 Jun, 2016 2 commits
-
-
jspraul authored
Fix an MSYS2-build-breaking error: unknown type name ‘fd_set’
-
Yossi Gottlieb authored
module.
-
- 05 Jun, 2016 7 commits
-
-
Pierre Chapuis authored
-
Pierre Chapuis authored
-
Pierre Chapuis authored
-
Pierre Chapuis authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 04 Jun, 2016 2 commits
- 03 Jun, 2016 3 commits
- 01 Jun, 2016 2 commits