Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 10 Sep 2015 20:33:45 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12863191.1441917204000.306436.1441917225684@Atlassian.JIRA>
In-Reply-To: <JIRA.12863191.1441917204000@Atlassian.JIRA>
References: <JIRA.12863191.1441917204000@Atlassian.JIRA>
 <JIRA.12863191.1441917204071@arcas>
Subject: [jira] [Created] (HBASE-14401) Stamp failed appends with sequenceid
 too.... Cleans up latches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

stack created HBASE-14401:
-----------------------------

             Summary: Stamp failed appends with sequenceid too.... Cleans up latches
                 Key: HBASE-14401
                 URL: https://issues.apache.org/jira/browse/HBASE-14401
             Project: HBase
          Issue Type: Sub-task
          Components: test, wal
            Reporter: stack
            Assignee: stack


Looking in test output I see we can sometimes get stuck waiting on sequenceid... The parent issues redo of our semantic makes it so we encounter failed append more often around damaged WAL.

This patch makes it so we stamp sequenceid always, even if the append fails. This way all sequenceids are accounted for but more important, the latch on sequenceid down in WALKey will be cleared.. where before it was not being cleared (there is no global list of outstanding WALKeys waiting on sequenceids so no way to clean them up... we don't need such a list if we ALWAYS stamp the sequenceid).


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