kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6514) Add API version as a tag for the RequestsPerSec metric
Date Tue, 06 Feb 2018 22:08:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354625#comment-16354625

Ismael Juma commented on KAFKA-6514:

Thanks for the JIRA [~allenxwang]. Agreed that this would be useful. A couple of comments/questions:
 # For compatibility reasons, we may consider keeping the metric without a version and add
new metrics with the version tag.
 # We need a simple KIP since this affects metrics, which are public interfaces.
 # Given that the KIP freeze for 1.1.0 was on 23 January ([https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75957546),] this
would have to target the next release.

> Add API version as a tag for the RequestsPerSec metric
> ------------------------------------------------------
>                 Key: KAFKA-6514
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6514
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.0
>            Reporter: Allen Wang
>            Priority: Major
> After we upgrade broker to a new version, one important insight is to see how many clients
have been upgraded so that we can switch the message format when most of the clients have
also been updated to the new version to minimize the performance penalty. 
> RequestsPerSec with the version tag will give us that insight.

This message was sent by Atlassian JIRA

View raw message