- 05 May, 2016 19 commits
- 
- 
antirez authored
- 
antirez authored
- 
Salvatore Sanfilippo authoredUpdate global protection error message 
- 
Ruben Bridgewater authored
- 
Salvatore Sanfilippo authoredFix a possible race condition of sdown event detection if sentinel's connection to master/slave/sentinel became disconnected just after the last PONG and before the next PING. 
- 
Salvatore Sanfilippo authoredfix linux compile Error zmalloc.c:109: error: invalid lvalue in unary `&' 
- 
Salvatore Sanfilippo authoredFix nanosecond conversion 
- 
antirez authored
- 
antirez authored
- 
Salvatore Sanfilippo authoredFixes a typo in the comments 
- 
Salvatore Sanfilippo authoredFix for #3076 Reverse redirect address parse 
- 
antirez authoredThanks to @tushar2708 for the PR. I applied a slightly different fix. Thanks to @cespare for reporting. Close #3024 Close #3020 
- 
antirez authored
- 
Chris Thunes authoredFixes #2515. 
- 
Salvatore Sanfilippo authoredmaxmemory_policy fix for #3187 
- 
Salvatore Sanfilippo authoredFixed typo in README.md 
- 
Salvatore Sanfilippo authoredFix redis-trib.rb 
 
- 
- 04 May, 2016 7 commits
- 
- 
antirez authoredSometimes Redis patch releases are released in a matter of weeks or days one after the other. In order to have less release friction the idea is to stop writing changelogs by hand, in order to also cover everything interesting there is to say. Useless things can be deleted manually by the changelog. Also this gives more credits to contributors since often in the commit message involved people are cited even when they are not the authors of the commit. 
- 
antirez authored
- 
antirez authoredThanks to @oranagra for the idea of allowing CONFIG GET during loading. 
- 
antirez authoredThanks to @oranagra for the hint about misplaced 'r' flags. 
- 
antirez authored
- 
Salvatore Sanfilippo authoredMinor fixes found during merge and code review 
- 
antirez authoredThanks to @tidwall for reporting. Close #3194. 
 
- 
- 02 May, 2016 2 commits
- 
- 
antirez authoredThe test works but is very slow so far, since it involves resharding 1/5 of all the cluster slots from master 0 to the other 4 masters and back into the original master. 
- 
antirez authoredThis fixes issue #3043. Before this fix, after a complete resharding of a master slots to other nodes, the master remains empty and the slaves migrate away to other masters with non-zero nodes. However the old master now empty, is no longer considered a target for migration, because the system has no way to tell it had slaves in the past. This fix leaves the algorithm used in the past untouched, but adds a new rule. When a new or old master which is empty and without slaves, are assigend with their first slot, if other masters in the cluster have slaves, they are automatically considered to be targets for replicas migration. 
 
- 
- 30 Apr, 2016 1 commit
- 
- 
Seth Bergman authored
 
- 
- 25 Apr, 2016 6 commits
- 22 Apr, 2016 1 commit
- 
- 
therealbill authoredI've renamed maxmemoryToString to evictPolicyToString since that is more accurate (and easier to mentally connect with the correct data), as well as updated the function to user server.maxmemory_policy rather than server.maxmemory. Now with a default config it is actually returning the correct policy rather than volatile-lru. 
 
- 
- 18 Apr, 2016 2 commits
- 
- 
Salvatore Sanfilippo authoredFix ZINCRBY return value. 
- 
Damian Janowski authored
 
- 
- 15 Apr, 2016 2 commits