kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-3857) Additional log cleaner metrics
Date Sat, 14 Jan 2017 02:30:26 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jun Rao updated KAFKA-3857:
---------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.2.0
           Status: Resolved  (was: Patch Available)

Issue resolved by pull request 2378
[https://github.com/apache/kafka/pull/2378]

> Additional log cleaner metrics
> ------------------------------
>
>                 Key: KAFKA-3857
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3857
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Kiran Pillarisetty
>             Fix For: 0.10.2.0
>
>
> The proposal would be to add a couple of additional log cleaner metrics: 
> 1. Time of last log cleaner run 
> 2. Cumulative number of successful log cleaner runs since last broker restart.
> Existing log cleaner metrics (max-buffer-utilization-percent, cleaner-recopy-percent,
max-clean-time-secs, max-dirty-percent) do not differentiate an idle log cleaner from a dead
log cleaner. It would be useful to have the above two metrics added, to indicate whether log
cleaner is alive (and successfully cleaning) or not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message