You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@rocketmq.apache.org by "GenerousMan (via GitHub)" <gi...@apache.org> on 2023/03/24 08:33:31 UTC

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

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

   Yes, in such cases, triggering automatic switching can make things better. 
   I think it is possible to add health check in the master: When some fatal exceptions (such as IOException caused by disk problems) occur, the master can report to the controller and elect a new master——just as kafka did. Some non-fatal abnormal states may be recorded, which will contribute to the observability of HA.


-- 
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