[
https://issues.apache.org/jira/browse/KAFKA-16102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialun Peng updated KAFKA-16102:
--------------------------------
Description:
When I dynamically modify the parameters related to Kafka listeners, such as
changing the IP or port value of a listener, the dynamic parameters under the
corresponding path in ZooKeeper are updated. However, in reality, the
modification of the IP or port for the corresponding listener does not take
effect. This phenomenon consistently occurs. And there is a slight improvement
as the error "Security protocol cannot be updated for existing listener" will
be eliminated.
was:When I dynamically modify the parameters related to Kafka listeners, such
as changing the IP or port value of a listener, the dynamic parameters under
the corresponding path in ZooKeeper are updated. However, in reality, the
modification of the IP or port for the corresponding listener does not take
effect. This phenomenon consistently occurs. And there is a slight improvement
as the error "Security protocol cannot be updated for existing listener" will
be eliminated.
> about DynamicListenerConfig, the dynamic modification of the listener's port
> or IP does not take effect.
> --------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-16102
> URL: https://issues.apache.org/jira/browse/KAFKA-16102
> Project: Kafka
> Issue Type: Bug
> Components: config
> Affects Versions: 3.6.0
> Environment: Must be present in any environment.
> Reporter: Jialun Peng
> Assignee: Jialun Peng
> Priority: Minor
> Labels: easyfix
> Fix For: 3.8.0
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> When I dynamically modify the parameters related to Kafka listeners, such as
> changing the IP or port value of a listener, the dynamic parameters under the
> corresponding path in ZooKeeper are updated. However, in reality, the
> modification of the IP or port for the corresponding listener does not take
> effect. This phenomenon consistently occurs. And there is a slight
> improvement as the error "Security protocol cannot be updated for existing
> listener" will be eliminated.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
