[
https://issues.apache.org/jira/browse/KAFKA-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844721#comment-17844721
]
Justine Olshan commented on KAFKA-16264:
----------------------------------------
Thanks. I will take a look.
It just occurred to me that such a change may require a small KIP.
[https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals]
Let me double check and get back to you.
> Expose `producer.id.expiration.check.interval.ms` as dynamic broker
> configuration
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-16264
> URL: https://issues.apache.org/jira/browse/KAFKA-16264
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jorge Esteban Quilcate Otoya
> Assignee: Jorge Esteban Quilcate Otoya
> Priority: Major
>
> Dealing with a scenario where too many producer ids lead to issues (e.g. high
> cpu utilization, see KAFKA-16229) put operators in need to flush producer ids
> more promptly than usual.
> Currently, only the expiration timeout `producer.id.expiration.ms` is exposed
> as dynamic config. This is helpful (e.g. by reducing the timeout, less
> producer would eventually be kept in memory), but not enough if the
> evaluation frequency is not sufficiently short to flush producer ids before
> becoming an issue. Only by tuning both, the issue could be workaround.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
