Page History

...

If the client is bootstrapping, it does not supply ClusterId  or NodeId . After bootstrapping, during which is it learns the information from its initial Metadata  response, it supplies both.

...

An alternative would be to introduce a new Connect  RPC into the Kafka protocol, rather than extending ApiVersions . This would naturally extend to support new features such as multi-tenancy and namespaces in the future. We probably would not want to add additional context such as a namespace onto ApiVersions  , so maybe we should bite the bullet now and add a new RPC. Part of the motivation of this KIP is to start the discussion in the community about the relative merits.

It would also be possible to carry node information in every RPC. That would allow individually misrouted packets to be diagnosed, but this KIP is not trying to handle situations in which the packets being sent to a broker are routed in different directions by a proxy or similar.