aruraghuwanshi opened a new issue, #17730: URL: https://github.com/apache/druid/issues/17730
### Affected Version 28.0.1 ### Description After the coordinator leader election is concluded, sometimes the old coordinator leader keeps emitting stale metrics for a specific datasource, despite the new coordinator leader emitting the realtime metrics. This creates duplication and erroneous reporting. Some details that were noted: - Its always the high ingestion volume datasource that goes into this problem state with 2 coordinators emitting that metric (One stale and one actual). All other datasources' metrics are emitted only by the new coordinator-leader. - No difference in logs emitted by the old coordinator leader for the problematic datasource vs the good ones. Reference Image attached (Blue: Old coordinator metric for one specific datasource in a stuck/stale state; Green: New coordinator emitting the same metric with the realtime values) <img width="1678" alt="Image" src="https://github.com/user-attachments/assets/d1988086-d3f5-464e-b0ba-69ec003dd17f"; /> -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
