[
https://issues.apache.org/jira/browse/KUDU-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Percy updated KUDU-559:
----------------------------
Parent: KUDU-808
> Reject/timeout requests when consensus majority is down
> -------------------------------------------------------
>
> Key: KUDU-559
> URL: https://issues.apache.org/jira/browse/KUDU-559
> Project: Kudu
> Issue Type: Sub-task
> Components: consensus
> Affects Versions: M5
> Reporter: Todd Lipcon
> Assignee: Adar Dembo
> Priority: Critical
>
> Currently, if a node is the leader but the majority of nodes in the quorum
> have crashed, it still allows writers to submit messages to the consensus
> queue, and never times them out. Eventually the queue starts filling up and
> callers will receive "queue full" errors, but the RPCs associated with the
> messages stuck in the queue never get responded to. Instead, they should be
> timed out or otherwise responded to more quickly.
> We also need to handle the case where an old leader has become partitioned
> from its quorum. It needs to at some point discover that it hasn't
> successfully heartbeat in longer than the election timeout, and step down on
> its own, or else clients may continually access it and not ever detect that
> they need to go find the new leader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
