Page History

...

While the early access release of JBOD in KRaft offers the opportunity to try out this new feature, it is important to be aware of the following limitations:

• Log directory failure At least two known bugs can cause log directory failures to re-creates create partitions in another logdir automatically : When a single log directory fails and then is subsequently brought back on line, the restart of the broker will fail because the same partitions will occur in two different directories. This issue is tracked in can also happen as a combination of intra-broker replica movement and log directory failure. These issues are tracked in

  Jira
  server ASF JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-16234

  and 

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-16082

  .
• A race condition while promoting a future replica, as a result of intra-broker replica reassignment, can lead to unavailability.

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-16297

For the latest information regarding known issues, their resolutions, and possible workarounds, please visit the parent tracker for KRaft JBOD follo-ups and improvements at