DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
If the client is bootstrapping, it does not supply ClusterId or NodeId . After bootstrapping, during which it learns the information from its initial Metadata response, it supplies both. When rebootstrapping begins, the client discards the cluster ID and node information that it learnt from its earlier Metadata response so that it can bootstrap from scratch.
The validation of ClusterId and NodeId is as follows:
...
The response schema is unchanged. ApiVersions is now able to return two additional existing errors codes: REBOOTSTRAP_REQUIRED and INCONSISTENT_CLUSTER_ID .
Configuration
Common client configuration
A low importance configuration is added just in case an unforeseen situation arises where the new checks introduced by this KIP cause problems with existing deployments. Kafka clients have always supported cluster ID change without requiring restart. By clearing cluster metadata when rebootstrapping begins, Kafka clients should be able to switch cluster ID safely which could be useful in disaster recovery scenarios.
| Configuration | Description | Values |
|---|---|---|
metadata.cluster.check.enable | Whether the client should send cluster and node information when connecting to a broker to enable it to check for a misrouted connection. | Boolean. true (default), or false |
Compatibility, Deprecation, and Migration Plan
...