One scenario in Redis cluster is that: 1. The new started host(slave) was added to the existing shard. 2. The slave will try to ask for full sync from the master 3. The master will fork a child process and execute BGSAVE.
There is issue that once step 1 finished, the new slave has started to serve traffics from clients, it will result in data miss as the new host has not completed the full sync(the data inconsistency between master and the new started slave).
I am wondering if there is way to prevent the not ready host serving traffics. The clients do not expect data miss caused by the not ready host.
Comment From: yossigo
This is related to #4624, but IIUC in a cluster settings we have an additional state where the node is up but replication did not even begin.
Comment From: ranshid
@yossigo @ackerL there is https://github.com/redis/redis/pull/9287 which was aiming to mask loading replicas from being discovered - maybe that can be used to help?
Comment From: ackerL
Thanks @ranshid, @yossigo , the same asking was mentioned in the #9287. It seems the Redis 7.0 has supported the feature and what we need to do is to upgrade the Redis version to version 7.0.
Comment From: zuiderkwast
Solved by #9287, as mentioned.