You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jorge Esteban Quilcate Otoya (Jira)" <ji...@apache.org> on 2024/02/16 08:20:00 UTC

[jira] [Created] (KAFKA-16264) Expose `producer.id.expiration.check.interval.ms` as dynamic broker configuration

Jorge Esteban Quilcate Otoya created KAFKA-16264:
----------------------------------------------------

             Summary: 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


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)