Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Having two configuration properties that must always hold the same value causes unnecessary confusion . The documentation describes and contradicts the documentation, which describes `node.id` as required in KRaft mode, yet the synonym mechanism allows users to omit node.id entirely if broker.id is set, contradicting the documented requirement.

Related ZooKeeper-era configurations such as broker.id.generation.enable and reserved.broker.max.id were already removed in Kafka 4.0, making broker.id the only remaining legacy identifier config. We should deprecate it to simplify the configuration surface and guide all users toward the single, canonical configuration: node.id.

...

Config

Type

Default

4.3

5.0

broker.id

INT

-1

Deprecated

Removed

node.id

INT

(required)

No change

No change

Note
titleNote

...

The documentation

...

describes node.id as required in KRaft mode, but it can currently be omitted if broker.id is set, because the synonym mechanism automatically populates node.id from broker.id. After the removal in 5.0, node.id must be explicitly set.


No changes to public APIs, network protocols, metrics, or command-line tools.

...