In the process of command propagation, one command is lost, while other commands are not lost. In this command propagation process, the slave node does not send ack to confirm offset. When sending ack, the offset does not correspond to that of the master node. The master node cannot recover data with the offset of the slave node. Will the master node re-generate rdb files via bgsave and then load the slave node
Please keep in mind that this issue tracker should be used for reporting bugs or proposing improvements to the Redis server.
Generally, questions about using Redis should be directed to the community:
It is also possible that your question was already asked here, so please do a quick issues search before submitting. Lastly, if your question is about one of Redis' clients, you may to contact your client's developers for help.
That said, please feel free to replace all this with your question :)
Comment From: oranagra
I don't understand the problem or scenario. what do you mean by command getting lost?
Comment From: Janmsstrive
I don't understand the problem or scenario. what do you mean by command getting lost?
Master/slave replication During command transmission, multiple write commands are transmitted in an ack response process, but one command is lost. How can master/slave maintain consistency
Comment From: oranagra
How / why would one command get lost? TCP connection doesn't lose bytes, and if it did it wouldn't be a full command and the whole protocol / stream will get messed up.
Please describe the scenario better..
Comment From: Janmsstrive
How / why would one command get lost? TCP connection doesn't lose bytes, and if it did it wouldn't be a full command and the whole protocol / stream will get messed up.
Please describe the scenario better..
A write command is lost because of a network failure, not the partial bytes of the write command
Comment From: oranagra
There's no such thing. What you're describing (without enough detail) is impossible. Please get your facts right before using the title "BUG"