[GitHub] [rocketmq] odbozhou commented on issue #3661: Why only the last few files are synchronized when the master-slave synchronization gap is large

[GitBox <gi...@apache.org>]

odbozhou commented on issue #3661:
URL: https://github.com/apache/rocketmq/issues/3661#issuecomment-1001894165


   I understand that this problem occurs in two situations.
   
   - 1. The stand-alone machine changes to m-s mode. This is usually only a test, and it is generally unlikely to exist online.
   - 2. There are multiple groups of active and standby brokers online (at least 2m2s is recommended), and the standby machine is faulty and the standby machine needs to be replaced. If this happens, it is recommended that the master broker set write prohibition, and after 3 days (determine the specific time according to the setting message save time), rebuild the group of brokers.
   If you change the slave, start synchronization from the broker, because the amount of synchronization is large, it is likely that the master broker is busy in synchronization, which makes the broker unavailable, so it is not recommended to replace the slave in this way.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org