ForIt111 opened a new issue, #11166: URL: https://github.com/apache/rocketmq/issues/11166
### Describe the Bug `TieredStoreMetricsManager` catches `ConsumeQueueException` while collecting the `dispatchBehind` and `dispatchLatency` gauges, then silently ignores the exception. The affected callbacks are in `initMetrics()`. When either collection path fails, the metric has no measurement for that collection cycle and the broker logs do not show the failure. Operators cannot distinguish a zero metric value from an unsuccessful collection attempt. `PopMetricsManager` logs `ConsumeQueueException` with `log.error(message, e)` for its gauge callbacks. Applying the same handling here keeps the metric callbacks non-disruptive while making failures observable. ### Expected Behavior Tiered Store metric collection failures should be logged with the exception details. ### Additional Context The proposed change only adds error logging in the two existing `catch (ConsumeQueueException e)` blocks. Normal metric collection and message processing behavior remain unchanged. -- 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]
