You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2015/09/10 18:45:46 UTC
[jira] [Created] (KAFKA-2530) metrics for old replica fetcher
thread need to be deregistered
Jun Rao created KAFKA-2530:
------------------------------
Summary: metrics for old replica fetcher thread need to be deregistered
Key: KAFKA-2530
URL: https://issues.apache.org/jira/browse/KAFKA-2530
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.8.2.1
Reporter: Jun Rao
Currently, the lag metrics in the replica fetcher has the following format where the leader broker id is included in the clientId tag.
clientId="ReplicaFetcherThread-0-101",partition="0",topic="test",mbean_property_type="FetcherLagMetrics",Value="262"
There are a couple of issues. (1) When the replica changes from a follower to a leader, we will need to set the lag to 0 or deregister the metric. (2) Similarly, when the follower switch to another leader, we should deregister the metric or clear the value. Also, we probably should remove the leader broker id from the clientId tag. That way, the metric name doesn't change when the follower switches leaders.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)