You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Michael Bingham (Jira)" <ji...@apache.org> on 2020/01/31 01:57:00 UTC

[jira] [Created] (KAFKA-9485) Dynamic updates to num.recovery.threads.per.data.dir are not applied right away

Michael Bingham created KAFKA-9485:
--------------------------------------

             Summary: Dynamic updates to num.recovery.threads.per.data.dir are not applied right away
                 Key: KAFKA-9485
                 URL: https://issues.apache.org/jira/browse/KAFKA-9485
             Project: Kafka
          Issue Type: Improvement
          Components: core, log
    Affects Versions: 2.4.0
            Reporter: Michael Bingham


The {{num.recovery.threads.per.data.dir}} broker property is a {{cluster-wide}} dynamically configurable setting, but it does not appear that it would have any dynamic effect on actual broker behavior.

The recovery thread pool is currently only created once when the {{LogManager}} is started and the {{loadLogs()}} method is called. If this property is later changed dynamically, it would have no effect until the broker is restarted.

This might be confusing to someone modifying this property, so perhaps should be made more clear in the documentation, or perhaps changed to a \{{read-only}} property. The only benefit I see to having it be a dynamic config property is that it can be applied once for the entire cluster, instead of individually specified in each broker's {{server.properties}} file.



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