You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by sh...@apache.org on 2024/04/12 06:50:16 UTC
(kafka) branch trunk updated: MINOR: Document JBOD limitation during migration (#15692)
This is an automated email from the ASF dual-hosted git repository.
showuon pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 31171d0791a MINOR: Document JBOD limitation during migration (#15692)
31171d0791a is described below
commit 31171d0791a350236d2e5e3d143c51fd73cd7532
Author: Igor Soarez <i...@soarez.me>
AuthorDate: Fri Apr 12 07:50:09 2024 +0100
MINOR: Document JBOD limitation during migration (#15692)
Document JBOD limitation during migration when log dir failure.
Reviewers: Luke Chen <sh...@gmail.com>, Chia-Ping Tsai <ch...@gmail.com>
---
docs/ops.html | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/ops.html b/docs/ops.html
index ce1e0b41095..fc8ae78740d 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3823,6 +3823,12 @@ foo
version</i> (also known as the <i>inter.broker.protocol.version</i>.) Please do not attempt to do this during
a migration, or you may break the cluster.</li>
<li>After the migration has been finalized, it is not possible to revert back to ZooKeeper mode.</li>
+ <li>
+ During the migration, if a ZK broker is running with multiple log directories,
+ any directory failure will cause the broker to shutdown.
+ Brokers with broken log directories will only be able to migrate to KRaft once the directories are repaired.
+ For further details refer to <a href="https://issues.apache.org/jira/browse/KAFKA-16431">KAFKA-16431</a>.
+ </li>
<li><a href="#kraft_missing">As noted above</a>, some features are not fully implemented in KRaft mode. If you are
using one of those features, you will not be able to migrate to KRaft yet.</li>
</ul>