THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| MBean name | Description |
|---|---|
| kafka.server:type=KafkaServer,name=MetadataType | An enumeration of: ZooKeeper (1), Dual (2), KRaft (3). Each broker reports this. |
| kafka.controller:type=KafkaController,name=MigrationState | An enumeration of the possible migration states the cluster can be in. This is only reported by the active controller. The "ZooKeeper" and "MigrationEligible" states are reported by the ZK controller, while the remaining states are reported by the KRaft controller. |
| kafka.controller:type=KafkaController,name=ZooKeeperWriteBehindLag | The amount of lag in records that ZooKeeper is behind relative to the highest committed record in the metadata log. This metric will only be reported by the active KRaft controller. |
...
MetadataVersion (IBP)
A new metadata.version will be used for a few things in this design.
...
All brokers must be running this metadata.version before the migration can begin.
...
Configuration
A new “kafka.metadata.migration.enable” config will be added for the broker and controller. Its default will be “false”. Setting this config to “true” on the brokers is a prerequisite to starting the migration. Setting this to "true" on the KRaft controllers is the trigger for starting the migration (more on that below).
...