This is an early access release for JBOD in KRaft (KIP-858), and it is not recommended for use in production environments. Instead, we advise users to create new clusters with version 3.7.0-IV2 and test the feature there. Alternatively, you can try the JBOD storage feature on existing non-production clusters upgrading them to version 3.7.0-IV2 or upgrading existing non-production cluster running JBOD in Zk to version 3.7.0-IV2 and then migrating them to KRaft.

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 re-creates 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 

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 . We are committed to addressing these issues and providing a reliable JBOD in KRaft experience, and your feedback is incredibly valuable in helping us improve the feature.