You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Brian Lueck (JIRA)" <ji...@apache.org> on 2016/04/28 00:35:12 UTC
[jira] [Created] (KAFKA-3632) ConsumerLag metrics persist after
partition migration
Brian Lueck created KAFKA-3632:
----------------------------------
Summary: ConsumerLag metrics persist after partition migration
Key: KAFKA-3632
URL: https://issues.apache.org/jira/browse/KAFKA-3632
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.9.0.1, 0.8.2.2
Environment: JDK 1.8, Linux
Reporter: Brian Lueck
Priority: Minor
When a partition is migrated away from a broker, the ConsumerLag metric for the topic/partition gets 'stuck' at the current value. The only way to remove the metric is to restart the broker.
This appears to be because in AbstractFetcherThread.scala there is no way of removing a metric. See...
{code}
class FetcherLagStats(metricId: ClientIdAndBroker) {
private val valueFactory = (k: ClientIdTopicPartition) => new FetcherLagMetrics(k)
val stats = new Pool[ClientIdTopicPartition, FetcherLagMetrics](Some(valueFactory))
def getFetcherLagStats(topic: String, partitionId: Int): FetcherLagMetrics = {
stats.getAndMaybePut(new ClientIdTopicPartition(metricId.clientId, topic, partitionId))
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)