iamqq23ue commented on issue #3661:
URL: https://github.com/apache/rocketmq/issues/3661#issuecomment-1001930649
I understand that this problem occurs in two situations.
The stand-alone machine changes to m-s mode. This is usually only a test,
and it is generally unlikely to exist online.
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.
您好。在我看来，如果一个slave故障且无法恢复，我们可以直接创建一个新的slave同步数据，否则单点运行几天更不适合实际的生产环境。
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
