- 18 Dec, 2017 1 commit
-
-
antirez authored
See #3462 and related PRs. We use a simple algorithm to calculate the level of affinity violation, and then an optimizer that performs random swaps until things improve.
-
- 09 Oct, 2016 1 commit
-
-
yyoshiki41 authored
-
- 23 Jun, 2016 1 commit
-
-
rojingeorge authored
Display the nodes summary once the cluster is established using redis-trib.rb After the cluster meet and join was done, when the summary was shown, it was giving info regarding the nodes. This fix ensures that confusion where the slaves were shown as masters. Fix would be to reset the nodes and reload the cluster information before checking the cluster status after creating it.
-
- 04 Apr, 2016 1 commit
-
-
antirez authored
This fix was suggested by Anthony LaTorre, that provided also a good test case that was used to verify the fix. The problem with the old implementation is that, the time returned by a timer event (that is the time after it want to run again) is added to the event *start time*. So if the event takes, in order to run, more than the time it says it want to be scheduled again for running, an infinite loop is triggered.
-
- 30 Mar, 2016 2 commits
-
-
Ryosuke Hasebe authored
-
Ryosuke Hasebe authored
-
- 02 Feb, 2016 1 commit
-
-
antirez authored
-
- 13 Jan, 2016 1 commit
-
-
antirez authored
Because of rounding error even with weight=0 sometimes a node was left with an assigned slot. Close #3001.
-
- 12 Jan, 2016 1 commit
-
-
antirez authored
-
- 11 Jan, 2016 4 commits
- 02 Jan, 2016 1 commit
-
-
antirez authored
-
- 18 Dec, 2015 2 commits
- 15 Dec, 2015 3 commits
- 14 Dec, 2015 1 commit
-
-
antirez authored
-
- 11 Dec, 2015 3 commits
-
-
antirez authored
We use the new variadic/pipelined MIGRATE for faster migration. Testing is not easy because to see the time it takes for a slot to be migrated requires a very large data set, but even with all the overhead of migrating multiple slots and to setup them properly, what used to take 4 seconds (1 million keys, 200 slots migrated) is now 1.6 which is a good improvement. However the improvement can be a lot larger if: 1. We use large datasets where a single slot has many keys. 2. By moving more than 10 keys per iteration, making this configurable, which is planned. Close #2710 Close #2711
-
antirez authored
-
daniele authored
redis-trib.rb: --timeout XXXXX option added to fix and reshard commands. Defaults to 15000 milliseconds
-
- 14 Oct, 2015 2 commits
-
-
David Thomson authored
-
David Thomson authored
-
- 09 Oct, 2015 1 commit
-
-
antirez authored
Kinda related to #2770.
-
- 08 Jan, 2015 2 commits
-
-
Matt Stancliff authored
-
Matt Stancliff authored
Under certain conditions the node list wasn't being fully populated and 'create' would fail trying to call methods on nil objects.
-
- 20 Dec, 2014 1 commit
-
-
Matt Stancliff authored
This tiny bit of code has gone through so many revisions. Hopefully it's more correct now. Fixes #2204
-
- 29 Oct, 2014 2 commits
-
-
Matt Stancliff authored
-
Matt Stancliff authored
IP format is now any of: - 127.0.0.1:6379 - ::1:6379
-
- 26 Sep, 2014 1 commit
-
-
antirez authored
-
- 21 Jul, 2014 1 commit
-
-
antirez authored
-
- 18 Jul, 2014 1 commit
-
-
antirez authored
The introduction of --from --to --slots --yes options allow to reshard from cli in an automated way from scripts. The code is ugly and needs refactoring as soon as we get it in RC / stable release.
-
- 21 May, 2014 3 commits
- 12 May, 2014 3 commits
-
-
antirez authored
This way there is no need for the conflict resolution algo to be used in order to start with a cluster where each node has a different configEpoch.
-
antirez authored
-
antirez authored
Will be configurable / adaptive at some point but let's start with a saner value compared to 1 sec which is not a good idea for big data structures stored into a single key.
-