[
https://issues.apache.org/jira/browse/KAFKA-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832187#comment-16832187
]
Vahid Hashemian commented on KAFKA-8119:
----------------------------------------
Removed Fix Version 2.2.1 as this issue is not blocking that release.
> KafkaConfig listener accessors may fail during dynamic update
> -------------------------------------------------------------
>
> Key: KAFKA-8119
> URL: https://issues.apache.org/jira/browse/KAFKA-8119
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.2.0
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 2.3.0
>
>
> Noticed a test failure in DynamicBrokerReconfigurationTest where the test
> accessing `KafkaConfig#listeners` during dynamic update of listeners threw an
> exception. In general, most dynamic configs can be updated independently, but
> listeners and listener security protocol map need to be updated together when
> new listeners that are not in the map are added or an entry is removed from
> the map along with the listener. We don't expect to see this failure in the
> implementation code because dynamic config updates are on a single thread and
> SocketServer processes the full update together and validates the full config
> prior to applying the changes. But we should ensure that
> KafkaConfig#listeners, KafkaConfig#advertisedListeners etc. work even if a
> dynamic update occurs during the call since these methods are used in tests
> and could potentially be used in implementation code in future from different
> threads.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
