You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/10/09 18:28:00 UTC

[jira] [Commented] (KAFKA-10242) Adding metrics to track the total count of idempotent producers that Broker need to track

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

Bill Bejeck commented on KAFKA-10242:
-------------------------------------

Since this Jira requires a KIP, as part of the 2.7.0 release process I'm going to remove the "fix version" field.  When we have an approved KIP for this we can fill out the fix version at that point.

> Adding metrics to track the total count of idempotent producers that Broker need to track
> -----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-10242
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10242
>             Project: Kafka
>          Issue Type: Improvement
>          Components: producer 
>    Affects Versions: 2.5.0
>            Reporter: Ming Liu
>            Priority: Critical
>              Labels: needs-kip
>             Fix For: 2.7.0
>
>
> We found it is very useful to track the total number of idempotent producers that broker is tracking.
> In our production environment, we have many idempotent producers for a cluster and sometimes that number increased to very high number which requires some attention to mitigate.
> This is especially true for client (< 2.4) where the client retry might generate too many different idempotent producers which can trigger broker GC.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)