Aru Raghuwanshi
Aru Raghuwanshi
> I had previously solved similar issue, by adding tiers in historicals. As of now operator is not aware of tiers, its only aware of nodeTypes. If we add support...
Metrics reporter was marked closed for that datasource during the leader transition, but the stale metrics are still being emitted by the old-coordinator leader.
Attached two examples here. I'm referring to all the mentioned druid metrics in [this Kafka section](https://druid.apache.org/docs/latest/operations/metrics/#ingestion-metrics-for-kafka)
Adding the metric names here for reference @kfaraz : ingest/kafka/lag ingest/kafka/maxLag ingest/kafka/avgLag ingest/kafka/partitionLag
For more context, we've faced this issue a few times before and the only resolution seems to be to kill the old-coordinator leader pod. Once that pod restarts and stabilizes...
Hey @kfaraz , unfortunately we're not emitting the heartbeat metric but we did confirm that we only had **one** active-leader at the time of this Incident, as per the logs...