Discussion:
[redis-db] Can you force a full resync from master to replica? Redis 4.0.11
Sidd S
2018-10-24 13:28:13 UTC
Permalink
What's the easiest way to force a full resync (as opposed to psync) from a
master to a replica? I am using Redis 4, running Redis Cluster. I'm able to
do this on 4.0.1 by exploiting a bug
(https://github.com/antirez/redis/pull/4607) , which seems to have been
fixed in a later version.

I am trying to investigate a potential bug where (on 4.0.1)
1. A slave tries to full-sync with a master node
2. The sync takes so long, it goes on longer for the (node-timeout *
replica-validity-factor) + repl-ping-replica-period

3.The master turns off mid-sync

4.The slave is unable to failover and the cluster is in a failing state.


I want to check to see if the above occurs on 4.0.11, but I'm not sure how to force a full sync.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
s***@gmail.com
2018-10-26 03:25:12 UTC
Permalink
On the replica, call *SLAVEOF NO ONE* to stop the replication. Then call *SLAVEOF
host port *to re-sync from master.


圚 2018幎10月24日星期䞉 UTC+8䞋午9:28:13Sidd S写道
Post by Sidd S
What's the easiest way to force a full resync (as opposed to psync) from a
master to a replica? I am using Redis 4, running Redis Cluster. I'm able to
do this on 4.0.1 by exploiting a bug (
https://github.com/antirez/redis/pull/4607) , which seems to have been
fixed in a later version.
I am trying to investigate a potential bug where (on 4.0.1)
1. A slave tries to full-sync with a master node
2. The sync takes so long, it goes on longer for the (node-timeout *
replica-validity-factor) + repl-ping-replica-period
3.The master turns off mid-sync
4.The slave is unable to failover and the cluster is in a failing state.
I want to check to see if the above occurs on 4.0.11, but I'm not sure how to force a full sync.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Sidd S
2018-10-26 11:14:45 UTC
Permalink
That is clever =) thank you!!!
Post by s***@gmail.com
On the replica, call *SLAVEOF NO ONE* to stop the replication. Then call *SLAVEOF
host port *to re-sync from master.
圚 2018幎10月24日星期䞉 UTC+8䞋午9:28:13Sidd S写道
Post by Sidd S
What's the easiest way to force a full resync (as opposed to psync) from
a master to a replica? I am using Redis 4, running Redis Cluster. I'm able
to do this on 4.0.1 by exploiting a bug (
https://github.com/antirez/redis/pull/4607) , which seems to have been
fixed in a later version.
I am trying to investigate a potential bug where (on 4.0.1)
1. A slave tries to full-sync with a master node
2. The sync takes so long, it goes on longer for the (node-timeout *
replica-validity-factor) + repl-ping-replica-period
3.The master turns off mid-sync
4.The slave is unable to failover and the cluster is in a failing state.
I want to check to see if the above occurs on 4.0.11, but I'm not sure how to force a full sync.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+***@googlegroups.com.
To post to this group, send email to redis-***@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.
Loading...