[
https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407769#comment-16407769
]
ASF GitHub Bot commented on KAFKA-6680:
---------------------------------------
rajinisivaram closed pull request #4740: MINOR: Document workaround for
KAFKA-6680 for 1.1
URL: https://github.com/apache/kafka/pull/4740
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/configuration.html b/docs/configuration.html
index df58ba76b77..7b975ba1d57 100644
--- a/docs/configuration.html
+++ b/docs/configuration.html
@@ -189,6 +189,12 @@ <h5>Adding and Removing Listeners</h5>
Inter-broker listener must be configured using the static broker
configuration <code>inter.broker.listener.name</code>
or <code>inter.broker.security.protocol</code>.
+ <p><b>Note:</b> In Kafka version 1.1.0, thread config updates and listener
updates are processed by a broker only if at least one other
+ broker config was configured dynamically prior to this update. To workaround
this issue, a dummy property may be dynamically configured
+ prior to an update of thread/listener configs or the update may be retried
after reverting the change. Dynamic update of listeners in
+ 1.1.0 requires <code>listener.security.protocol.map</code> to be updated to
a map containing security protocols for all the listeners,
+ even if listener name is a security protocol. These issues will be fixed in
the next release.
+
<h3><a id="topicconfigs" href="#topicconfigs">3.2 Topic-Level
Configs</a></h3>
Configurations pertinent to topics have both a server default as well an
optional per-topic override. If no per-topic configuration is given the server
default is used. The override can be set at topic creation time by giving one
or more <code>--config</code> options. This example creates a topic named
<i>my-topic</i> with a custom max message size and flush rate:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix config initialization in DynamicBrokerConfig
> ------------------------------------------------
>
> Key: KAFKA-6680
> URL: https://issues.apache.org/jira/browse/KAFKA-6680
> Project: Kafka
> Issue Type: Bug
> Reporter: Manikumar
> Assignee: Manikumar
> Priority: Major
> Fix For: 1.2.0
>
>
> Below issues observed while testing dynamic config update feature
> 1. {{kafkaConfig}} doesn't get updated during {{initialize}} if there are no
> dynamic configs defined in ZK.
> 2. update DynamicListenerConfig.validateReconfiguration() to check new
> Listeners must be subset of listener map
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
