• Dynamic Kafka Configurations


    Some of the Apache Kafka® broker and topic configurations can be updated without restarting the broker. This section talks about updating these configuration options dynamically and securing password configurations by storing them in encrypted form in ZooKeeper.

    Changing Broker Configurations Dynamically

    Some of the broker configurations can be updated without restarting the broker. See the Dynamic Update Mode option in Broker Configurations for the update mode of each broker configuration.

    • read-only: Requires a broker restart for update.
    • per-broker: May be updated dynamically for each broker.
    • cluster-wide: May be updated dynamically as a cluster-wide default. May also be updated as a per-broker value for testing.

    To alter the current broker configurations for broker ID 0 (for example, the number of log cleaner threads):

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --add-config log.cleaner.threads=2
    

    To alter several configurations at the same time, or to alter configurations with complex values (for example, the Router config for Audit Logs), create a file with the desired values in .properties format and use --add-config-file. If you have the new configurations in a file named new.properties:

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-default --alter --add-config-file new.properties
    

    To describe the current dynamic broker configs for broker ID 0:

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --describe
    

    To delete a configuration override and revert to the statically configured or default value for broker ID 0 (for example, the number of log cleaner threads):

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-name 0 --alter --delete-config log.cleaner.threads
    

    Some configurations may be configured as a cluster-wide default to maintain consistent values across the whole cluster. All brokers in the cluster will process the cluster default update. For example, to update log cleaner threads on all brokers:

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-default --alter --add-config log.cleaner.threads=2
    

    To describe the currently configured dynamic cluster-wide default configurations:

    bin/kafka-configs --bootstrap-server localhost:9092 --entity-type brokers --entity-default --describe
    

    All configurations that are configurable at cluster level may also be configured at per-broker level (e.g. for testing). If a configuration value is defined at different levels, the following order of precedence is used:

    • Dynamic per-broker config stored in ZooKeeper
    • Dynamic cluster-wide default config stored in ZooKeeper
    • Static broker config from server.properties
  • 相关阅读:
    hive中concat_ws的秘密
    C 语言中关键字const
    Shiro-SpringBoot (一)
    总结|8月日更挑战 - YOUR LIFE MATTERS
    基于51的单片机GPS定位系统设计
    (硅谷课堂项目)Java开发笔记1:MyBatis-Plus使用
    一行日志,让整个文件导出服务导出内容都为空..
    Trainer--学习笔记
    前后端分离不可忽视的陷阱,深入剖析挑战,分享解决方案,助你顺利实施分离开发。
    【微服务】Day12(搜索功能、Quartz)
  • 原文地址:https://blog.csdn.net/qq_32907195/article/details/126488579