[
https://issues.apache.org/jira/browse/KAFKA-17077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17077.
------------------------------------
Fix Version/s: 3.9.0
Resolution: Fixed
> the node.id is inconsistent to broker.id when
> "broker.id.generation.enable=true"
> --------------------------------------------------------------------------------
>
> Key: KAFKA-17077
> URL: https://issues.apache.org/jira/browse/KAFKA-17077
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: TengYao Chi
> Priority: Critical
> Fix For: 3.9.0
>
>
> We change the broker id of `KafkaConfig` directly when
> `broker.id.generation.enable=true` [0]. However, the update is NOT sync to
> node.id of `KafkaConfig`. It results in following issues:
> 1. we can see many "-1" in the log. for example:
> {code:sh}
> [2024-07-03 19:23:08,453] INFO [ExpirationReaper--1-AlterAcls]: Starting
> (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
> {code}
> 2. `KafkaRaftManager` will use uninitialized node.id to create
> `KafkaRaftClient` in migration [1], and the error sequentially happens
> [0]
> https://github.com/apache/kafka/blob/27220d146c5d043da4adc3d636036bd6e7b112d2/core/src/main/scala/kafka/server/KafkaServer.scala#L261
> [1]
> https://github.com/apache/kafka/blob/27220d146c5d043da4adc3d636036bd6e7b112d2/core/src/main/scala/kafka/raft/RaftManager.scala#L230
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
