Page History

...

You can then use the kafka-configs.sh tool to described the cordoned log directories:
$ bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --entity-type brokers --entity-name 0
Dynamic configs for broker 0 are:
  cordoned.log.dirs=/tmp/kraft-broker0-logs0 sensitive=false synonyms={DYNAMIC_BROKER_CONFIG:cordoned.log.dirs=/tmp/kraft-broker0-logs0}

You can use the same mechanism to uncordoned a log directory. Either update the broker's properties file and restart it, or use the kafka-configs.sh tool to update cordoned.log.dirs.

When the configuration is set on a broker, the broker will include the Uuids of cordoned log directories when it registers to the controller and also include them in each heartbeat request it sends to the controller to reflect potential dynamic updates.

...

• BrokerHeartbeatResponse v1 adds no new fields
  

Metadata Records

Updating these metadata records ensure that the cordoned log directories of each broker are persisted in the metadata log. So if a broker is offline its cordoned log directories are still available to the controller when assigning partitions.

• BrokerRegistrationChangeRecord v3 adds the CordonedLogDirs field

...