THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
If log directory that holds the cluster metadata topic is configured separately to a different path — using metadata.log.dir — then this log directory is does not get a UUID assigned.
| Footnote |
|---|
The broker cannot run if this particular log directory is unavailable, and when configured separately it cannot host any user partitions, so there's no point in identifying it in the Controller. |
Metadata records
RegisterBrokerRecord and BrokerRegistrationChangeRecord will both have two new fields:
...
{ "name": "Replicas", "type": "[]int32", "versions": "0", "entityType": "brokerId",
"about": "The replicas of this partition, sorted by preferred order." },
(...)
{ "name": "Assignment", "type": "[]ReplicaAssignment", "versions": "1+",
"about": "The replicas of this partition, sorted by preferred order.", "fields": [
{ "name": "Broker", "type": "int32", "versions": "1+", "entityType": "brokerId",
"about": "The broker ID hosting the replica." },
{ "name": "Directory", "type": "uuid", "versions": "1+", "taggedVersions": "+1", "tag": "0",
"about": "The log directory hosting the replica" }
]}
Although not explicitly specified in the schema, the default value for Directory is Uuid.ZERO, as that's the default default value for UUID types.
| Footnote |
|---|
Yes, double default, not a typo. The default setting, for the default value of the field. |
RPC requests
BrokerRegistrationRequest will include the following two new fields:
...