- 05 May, 2016 11 commits
-
-
Jan-Erik Rediger authored
1 microsecond = 1000 nanoseconds 1e3 = 1000 10e3 = 10000
-
Oran Agra authored
-
antirez authored
This 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.
-
antirez authored
-
antirez authored
-
David Cavar authored
Fix issue in case the redirect address is in ipv6 format. Parse from behind to extract last part of the response which represents actual port.
-
antirez authored
Thanks to @tushar2708 for the PR. I applied a slightly different fix. Thanks to @cespare for reporting. Close #3024 Close #3020
-
Salvatore Sanfilippo authored
Ensure slots are rechecked on EXEC.
-
Ryosuke Hasebe authored
-
Ryosuke Hasebe authored
-
- 11 Mar, 2016 1 commit
-
-
Chris Thunes authored
Fixes #2515.
-
- 10 Feb, 2016 2 commits
-
-
antirez authored
-
yoav@monfort.co.il authored
-
- 05 Feb, 2016 2 commits
-
-
antirez authored
-
Itamar Haber authored
-
- 31 Jan, 2016 3 commits
-
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
Removes more spuriousness from 3.0.7
-
- 30 Jan, 2016 1 commit
-
-
Itamar Haber authored
-
- 29 Jan, 2016 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
CLUSTER SLOTS now includes IDs in the nodes description associated with a given slot range. Certain client libraries implementations need a way to reference a node in an unique way, so they were relying on CLUSTER NODES, that is not a stable API and may change frequently depending on Redis Cluster future requirements.
-
antirez authored
Certain things were only applicable to 3.2.0 RC2 and RC3.
-
- 28 Jan, 2016 1 commit
-
-
antirez authored
We had to fix a few last minutes bugs.
-
- 26 Jan, 2016 6 commits
-
-
antirez authored
Reported here: https://www.reddit.com/r/redis/comments/42r0i0/avg_ttl_varies_a_lot/
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
The change covers the case where: 1. There is a node we can't reach (in fail or pfail state). 2. We see a different address for this node, in the gossip section sent to us by a node that, instead, is able to talk with the node we cannot talk to. In this case it's a good bet to switch to the address reported by this node, since there was an address switch and it is able to talk with the node and we are not. However previosuly this was done in a dangerous way, by initiating an handshake. The handshake, using the MEET packet, forces the receiver to join our cluster, and this is not a good idea. If the node in question really just switched address, but is the same node, it already knows about us, so we just need to perform an address update and a reconnection. So with this commit instead we just update the address of the node, release the node link if any, and attempt to reconnect in the next clusterCron() cycle. The commit also improves debugging messages printed by Cluster during address or ID switches.
-
antirez authored
-
- 25 Jan, 2016 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Centralize cleanup of newargv in a single place. Add more comments to help a bit following a complex function. Related to issue #3016.
-
antirez authored
Another leak was fixed in the case of syntax error by restructuring the allocation strategy for the two dynamic vectors. We also make sure to always close the cached socket on I/O errors so that all the I/O errors are handled the same, even if we had a previously queued error of a different kind from the destination server. Thanks to Kevin McGehee. Related to issue #3016.
-
antirez authored
In issue #3016 Kevin McGehee identified multiple very serious issues in the new implementation of MIGRATE. This commit attempts to restructure the code in oder to avoid mistakes, an analysis of the new implementation is in progress in order to check for possible edge cases.
-
antirez authored
-
antirez authored
-
antirez authored
With this commit we preserve the list of nodes that have .slaveof set to the node, even when the node is turned into a slave, and make sure to fix the .slaveof pointers to NULL when a node is freed from memory, regardless of the fact it's a slave or a master. Basically we try to remember the logical master in the current configuration even if the logical master advertised it as a slave already. However we still remember the associations, so that when a node is freed we can fix them. This should fix issue #3002.
-
antirez authored
-