[GitHub] [rocketmq] ShannonDing commented on issue #6468: The HA switch is not triggered when the broker disk I/O load is continuously high.

["ShannonDing (via GitHub)" <gi...@apache.org>]

ShannonDing commented on issue #6468:
URL: https://github.com/apache/rocketmq/issues/6468#issuecomment-1482437181

   Should we consider another scenario at the same time?
   
   When network jitter occurs, network reconnection may be triggered. In this case and in the view of the controller module, the broker channel will change.
   when the controller detects that the old channel is closed, it will directly kick the broker out of the brokerLiveTable and trigger a re-election. 
   
   At this point, the broker may reconnect quickly. Is it necessary to do a HA switching?


-- 
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: commits-unsubscribe@rocketmq.apache.org

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