You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/05/26 07:18:13 UTC

[jira] [Created] (KUDU-1469) Consensus can get "stuck" after a leader change when committed index is far behind replicated

Todd Lipcon created KUDU-1469:
---------------------------------

             Summary: Consensus can get "stuck" after a leader change when committed index is far behind replicated
                 Key: KUDU-1469
                 URL: https://issues.apache.org/jira/browse/KUDU-1469
             Project: Kudu
          Issue Type: Bug
          Components: consensus
    Affects Versions: 0.8.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon
            Priority: Critical


A YCSB stress test hit a bug whereby a tablet was "stuck" - operations were left in flight for hours/days and no progress could be made, despite a majority of replicas being alive.

Detailed analysis below.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)