hi I have replied on the PR that we should follow the deprecation cycle :)
Ming-Yen Chung <[email protected]> 於 2026年7月31日週五 下午1:48寫道： > Hi all, > > I've updated KIP-1232 to also cover the tiered storage plugin configs: > > RemoteLogManager passes broker.id to RemoteStorageManager and > RemoteLogMetadataManager via configure(). That's a plugin config rather > than the broker config, so it wasn't in the original scope, but leaving it > would keep broker.id alive in a public interface after the config is gone. > Both now also receive node.id with the same value; broker.id is still > passed in 4.4 and dropped in 5.0, so plugins have a release to migrate. > > Please let me know if you have any concerns. > > Best, > Ming-Yen > > Chia-Ping Tsai <[email protected]> 於 2026年4月6日週一 下午10:28寫道： > > > The KIP LGTM. Should we start the vote? > > > > On 2026/02/17 02:54:12 Ming-Yen Chung wrote: > > > Hi all, > > > > > > I would like to start a discussion on > > > KIP-1232: Deprecate broker.id config > > > <https://cwiki.apache.org/confluence/x/Hgp3Fw> > > > > > > With ZooKeeper removed in Kafka 4.0, node.id is the canonical node > > > identifier for all process roles. This KIP proposes to deprecate > > broker.id > > > from the server configuration in 4.3 and remove it in 5.0. > > > > > > Looking forward to your feedback. > > > > > > Best, > > > Ming-Yen > > > > > >
