RockteMQ-AI commented on issue #11045: URL: https://github.com/apache/rocketmq/issues/11045#issuecomment-5553420693
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** `BrokerHousekeepingService` registers a single `ChannelEventListener` that handles both `EXCEPTION` and `CLOSE` events by calling `controllerManager.unregisterBroker`. When a broker reconnects (new channel) and then an old stale channel closes, the stale `CLOSE` event unregisters the fresh registration, triggering a spurious master election. **Impact:** Controller broker management. Network partitions, slow clients, or reconnect storms cause legitimate masters to be evicted and trigger unnecessary elections, destabilizing the cluster. **Severity:** High — cluster stability and availability during network issues. **Fix Status:** PR #11046 scopes the unregistration to `EXCEPTION` events only, ignoring `CLOSE` events so that a stale close cannot evict a fresh registration. --- *Automated evaluation by RockteMQ-AI* -- 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]
