Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Is a cluster with replicas supported? #40

Open
1 task done
alrooney opened this issue Jan 17, 2021 · 0 comments
Open
1 task done

Question: Is a cluster with replicas supported? #40

alrooney opened this issue Jan 17, 2021 · 0 comments

Comments

@alrooney
Copy link

alrooney commented Jan 17, 2021

Report

Question: I have a redis cluster created from the bitnami helm chart here: https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster/#installing-the-chart with 3 master nodes and 3 replica nodes. I am trying to copy data from another redis cluster (with no replicas) into this cluster but I keep getting errors like this:

./rump -from redis://redis-telem-cache-stg-ksat-m-1-redis-cluster:6379 -to redis://10.255.8.12:6379 -ttl
r
signal: exit
rr
redis read: exit
MOVED 4042 10.255.8.14:6379

Note: Above 10.255.8.12:6379 is one of the master nodes.

$ kk exec rails-cache-stg-redis-ksat-m-1-redis-cluster-0 -- redis-cli --cluster check 10.255.8.10:6379
Defaulting container name to rails-cache-stg-redis-ksat-m-1-redis-cluster.
Use 'kubectl describe pod/rails-cache-stg-redis-ksat-m-1-redis-cluster-0 -n default-minim-private' to see all of the containers in this pod.
10.255.8.15:6379 (fbdd5a4e...) -> 14029 keys | 5462 slots | 1 slaves.
10.255.8.12:6379 (b3718ac7...) -> 568 keys | 5461 slots | 1 slaves.
10.255.8.14:6379 (8790c578...) -> 487 keys | 5461 slots | 1 slaves.
[OK] 15084 keys in 3 masters.
0.92 keys per slot on average.
>>> Performing Cluster Check (using node 10.255.8.10:6379)
S: 8500263462d98613bc6e1172106ddcd37f5976a6 10.255.8.10:6379
   slots: (0 slots) slave
   replicates b3718ac766349261d819c9923cd915fc43d70352
M: fbdd5a4eebe77b49ec984ec953ec098fe262d320 10.255.8.15:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
S: 4b371b26a9b5b3d0f23d2c965197f0bf3cbc355b 10.255.8.11:6379
   slots: (0 slots) slave
   replicates 8790c57879627039f3d74cc599e61707d33d93d4
M: b3718ac766349261d819c9923cd915fc43d70352 10.255.8.12:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
S: f01bd775618fd6de9a18160186a48a37b469da03 10.255.8.13:6379
   slots: (0 slots) slave
   replicates fbdd5a4eebe77b49ec984ec953ec098fe262d320
M: 8790c57879627039f3d74cc599e61707d33d93d4 10.255.8.14:6379
   slots:[0-5460] (5461 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.

Does rump currently support clusters with replicas? If it does can you recommend a way to diagnose/debug this further?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant