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/12/02 00:55:58 UTC

[jira] [Created] (KUDU-1779) Consensus "stuck" with all transaction trackers are at limit

Todd Lipcon created KUDU-1779:
---------------------------------

             Summary: Consensus "stuck" with all transaction trackers are at limit
                 Key: KUDU-1779
                 URL: https://issues.apache.org/jira/browse/KUDU-1779
             Project: Kudu
          Issue Type: Bug
          Components: consensus
    Affects Versions: 1.1.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon
            Priority: Critical


In a stress cluster, I saw one tablet get "stuck" in the following state:

- the transaction_tracker on all three replicas is "full" (no more can be submitted)
- leader elections proceed just fine, but no leader is able to advance the commit index

The issue seems to be that a replica will respond with 'CANNOT_PREPARE' when its transaction tracker is full. The leader then ignores this response, and doesn't advance the majority-replicated watermark. The transaction tracker stays full forever because the in-flight transactions can't get committed.

Notes to follow.



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