You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2024/08/27 23:49:00 UTC
[jira] [Commented] (KAFKA-14426) Add documentation for Kraft limtations that have open KIPs
[ https://issues.apache.org/jira/browse/KAFKA-14426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877209#comment-17877209 ]
Colin McCabe commented on KAFKA-14426:
--------------------------------------
> No online method of resizing the controller quorum
> No online method of recovering from controller disk loss
This was implemented in KIP-853
> No support for heterogeneous voter lists in running controller nodes
What is a "heterogeneous voter list"?
> When using a quorum size 3, there is no live-upgrade roll which is tolerant of a single unplanned machine failure.
The same issue exists in ZK with a quorum size of 3. This is why some people run with larger quorums
> When using a quorum size >3, there is a risk of zombie leaders causing extended outages without the pre-vote feature.
We have tested larger quorums and not found this to be the case. While pre-vote is a nice optimization, it is not needed to run quorums larger than 3.
> Add documentation for Kraft limtations that have open KIPs
> ----------------------------------------------------------
>
> Key: KAFKA-14426
> URL: https://issues.apache.org/jira/browse/KAFKA-14426
> Project: Kafka
> Issue Type: Task
> Components: documentation, kraft
> Reporter: Greg Harris
> Priority: Major
>
> Currently there are a number of limitations for Kraft, which are described as the motivation for the following open KIPs:
> * [https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes]
> * [https://cwiki.apache.org/confluence/display/KAFKA/KIP-856%3A+KRaft+Disk+Failure+Recovery]
> * [https://cwiki.apache.org/confluence/display/KAFKA/KIP-650%3A+Enhance+Kafkaesque+Raft+semantics#KIP650:EnhanceKafkaesqueRaftsemantics-Pre-vote]
> These limitations are:
> * No online method of resizing the controller quorum
> * No online method of recovering from controller disk loss
> * No support for heterogeneous voter lists in running controller nodes
> * When using a quorum size 3, there is no live-upgrade roll which is tolerant of a single unplanned machine failure.
> * When using a quorum size >3, there is a risk of zombie leaders causing extended outages without the pre-vote feature.
> These are significant enough concerns for operations of a Kraft-enabled cluster that they should be documented as official limitations in the ops documentation.
> Optionally, we may wish to provide or link to more detailed operations documentation about performing the offline-resize or offline-recovery stages, in addition to describing that such offline procedures are necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)