RockteMQ-AI commented on issue #4543: URL: https://github.com/apache/rocketmq-dashboard/issues/4543#issuecomment-5719785254
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified. The problem is well-documented with clear reproduction steps and a regression test. **Root Cause:** `RocketMQMetadataProvider.resolveConsumerConnection` returns `null` on unexpected Broker/NameServer errors, and the caller converts this to an empty instance list (`onlineInstances=0`). The Proxy fallback has the same ambiguity — it returns `null` both for explicit `CONSUMER_NOT_ONLINE` and for discovery/query failures. **Impact:** Studio diagnostics incorrectly report "有堆积但无在线客户端" (lag present but no online clients) when connection inventory is unavailable, leading to false UNHEALTHY assessments. This affects both web UI diagnostics and AI group-detail tool. **Severity:** High — user-visible data correctness issue affecting consumer group health monitoring. **Proposed Fix Scope:** - Use existing negative-sentinel convention (`onlineInstances=-1` for unavailable) - Add internal Proxy resolution status to distinguish explicit offline from lookup failure - Teach web/AI health diagnostics not to treat unavailable connection data as zero clients - Keep lag/consume-stat availability independent from connection-inventory availability An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
