[
https://issues.apache.org/jira/browse/KAFKA-16144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808548#comment-17808548
]
Mickael Maison edited comment on KAFKA-16144 at 1/19/24 9:11 AM:
-----------------------------------------------------------------
Marking this as a blocker as it's a regression and prevents running a cluster
with a single node in combined mode. Basically following the steps from the
[quickstart|https://kafka.apache.org/quickstart#quickstart_startserver] fails.
was (Author: mimaison):
Marking this as a blocker as it's a regression and prevents running a cluster
with a single node in combined node. Basically following the steps from the
[quickstart|https://kafka.apache.org/quickstart#quickstart_startserver] fails.
> Controller leader checkQuorum timer should skip only 1 controller case
> ----------------------------------------------------------------------
>
> Key: KAFKA-16144
> URL: https://issues.apache.org/jira/browse/KAFKA-16144
> Project: Kafka
> Issue Type: Bug
> Reporter: Luke Chen
> Assignee: Luke Chen
> Priority: Blocker
> Labels: newbie, newbie++
> Fix For: 3.7.0
>
>
> In KAFKA-15489, we fixed the potential "split brain" issue by adding the
> check quorum timer. This timer will be updated when the follower fetch
> request arrived. And it expires the timer when the there are no majority of
> voter followers fetch from leader, and resign the leadership.
> But in KAFKA-15489, we forgot to consider the case where there's only 1
> controller node. If there's only 1 controller node (and no broker node),
> there will be no fetch request arrived, so the timer will expire each time.
> However, if there's only 1 node, we don't have to care about the "check
> quorum" at all. We should skip the check for only 1 controller node case.
> Currently, this issue will happen only when there's 1 controller node and no
> any broker node (i.e. no fetch request sent to the controller).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
