Skip to content

Instantly share code, notes, and snippets.

@AlexMikhalev
Created May 10, 2021 11:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AlexMikhalev/9a2e32008eca94943475565697a6aa99 to your computer and use it in GitHub Desktop.
Save AlexMikhalev/9a2e32008eca94943475565697a6aa99 to your computer and use it in GitHub Desktop.
docker logs -f rgcluster
docker logs -f rgcluster
Starting 30001
Starting 30002
Starting 30003
Starting 30004
Starting 30005
Starting 30006
Starting 30007
Starting 30008
Starting 30009
Starting 30010
>>> Performing hash slots allocation on 10 nodes...
Master[0] -> Slots 0 - 3276
Master[1] -> Slots 3277 - 6553
Master[2] -> Slots 6554 - 9829
Master[3] -> Slots 9830 - 13106
Master[4] -> Slots 13107 - 16383
Adding replica 127.0.0.1:30007 to 127.0.0.1:30001
Adding replica 127.0.0.1:30008 to 127.0.0.1:30002
Adding replica 127.0.0.1:30009 to 127.0.0.1:30003
Adding replica 127.0.0.1:30010 to 127.0.0.1:30004
Adding replica 127.0.0.1:30006 to 127.0.0.1:30005
>>> Trying to optimize slaves allocation for anti-affinity
[WARNING] Some slaves are in the same host as their master
M: 2a4cefcb162fbcf78eb62e3c23009a98cf3ea26a 127.0.0.1:30001
slots:[0-3276] (3277 slots) master
M: 975d1900560e67660a698ab9861d7cb12de5ef6a 127.0.0.1:30002
slots:[3277-6553] (3277 slots) master
M: f949a5577d7a9733e3e7d6229b035510fc9b0105 127.0.0.1:30003
slots:[6554-9829] (3276 slots) master
M: db4d2f6514ad186dc49e743b9683dace0c3912e9 127.0.0.1:30004
slots:[9830-13106] (3277 slots) master
M: a9f71190d70e2cdecb8882892ba0afb60fc96ae8 127.0.0.1:30005
slots:[13107-16383] (3277 slots) master
S: f6c3f18925dbde7fc2a08242a9afc4da73b0976b 127.0.0.1:30006
replicates 2a4cefcb162fbcf78eb62e3c23009a98cf3ea26a
S: f2d82f96dce9eabcac448cbaad9bdc1e7ed83da9 127.0.0.1:30007
replicates db4d2f6514ad186dc49e743b9683dace0c3912e9
S: 6e8b7a249002374f203ce412e80257410c6faf3b 127.0.0.1:30008
replicates f949a5577d7a9733e3e7d6229b035510fc9b0105
S: 7eaab1e9d1fa671d689e4b9bda456454b025734c 127.0.0.1:30009
replicates a9f71190d70e2cdecb8882892ba0afb60fc96ae8
S: 8f5abe9d8094a061ce81a3e66d8d686007335c34 127.0.0.1:30010
replicates 975d1900560e67660a698ab9861d7cb12de5ef6a
Can I set the above configuration? (type 'yes' to accept): >>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
.
>>> Performing Cluster Check (using node 127.0.0.1:30001)
M: 2a4cefcb162fbcf78eb62e3c23009a98cf3ea26a 127.0.0.1:30001
slots:[0-3276] (3277 slots) master
1 additional replica(s)
S: 8f5abe9d8094a061ce81a3e66d8d686007335c34 192.168.80.3:30010
slots: (0 slots) slave
replicates 975d1900560e67660a698ab9861d7cb12de5ef6a
M: f949a5577d7a9733e3e7d6229b035510fc9b0105 192.168.80.3:30003
slots:[6554-9829] (3276 slots) master
1 additional replica(s)
S: 6e8b7a249002374f203ce412e80257410c6faf3b 192.168.80.3:30008
slots: (0 slots) slave
replicates f949a5577d7a9733e3e7d6229b035510fc9b0105
S: f2d82f96dce9eabcac448cbaad9bdc1e7ed83da9 192.168.80.3:30007
slots: (0 slots) slave
replicates db4d2f6514ad186dc49e743b9683dace0c3912e9
S: 7eaab1e9d1fa671d689e4b9bda456454b025734c 192.168.80.3:30009
slots: (0 slots) slave
replicates a9f71190d70e2cdecb8882892ba0afb60fc96ae8
S: f6c3f18925dbde7fc2a08242a9afc4da73b0976b 192.168.80.3:30006
slots: (0 slots) slave
replicates 2a4cefcb162fbcf78eb62e3c23009a98cf3ea26a
M: a9f71190d70e2cdecb8882892ba0afb60fc96ae8 192.168.80.3:30005
slots:[13107-16383] (3277 slots) master
1 additional replica(s)
M: 975d1900560e67660a698ab9861d7cb12de5ef6a 192.168.80.3:30002
slots:[3277-6553] (3277 slots) master
1 additional replica(s)
M: db4d2f6514ad186dc49e743b9683dace0c3912e9 192.168.80.3:30004
slots:[9830-13106] (3277 slots) master
1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Calling RG.REFRESHCLUSTER
127.0.0.1:30001: OK
192.168.80.3:30010: OK
192.168.80.3:30003: OK
192.168.80.3:30008: OK
192.168.80.3:30007: OK
192.168.80.3:30009: OK
192.168.80.3:30006: OK
192.168.80.3:30005: OK
192.168.80.3:30002: OK
192.168.80.3:30004: OK
==> 30001.log <==
==> 30002.log <==
==> 30003.log <==
==> 30004.log <==
==> 30005.log <==
==> 30006.log <==
==> 30007.log <==
==> 30008.log <==
==> 30009.log <==
==> 30010.log <==
Starting 30001
Starting 30002
Starting 30003
Starting 30004
Starting 30005
Starting 30006
Starting 30007
Starting 30008
Starting 30009
Starting 30010
Node 127.0.0.1:30001 replied with error:
LOADING Redis is loading the dataset in memory
Node 127.0.0.1:30001 replied with error:
LOADING Redis is loading the dataset in memory
Starting 30001
Starting 30002
Starting 30003
Starting 30004
Starting 30005
Starting 30006
Starting 30007
Starting 30008
Starting 30009
Starting 30010
Node 127.0.0.1:30001 replied with error:
LOADING Redis is loading the dataset in memory
Node 127.0.0.1:30001 replied with error:
LOADING Redis is loading the dataset in memory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment