You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 21:06:00 UTC

[jira] [Closed] (HBASE-14401) Stamp failed appends with sequenceid too.... Cleans up latches

     [ https://issues.apache.org/jira/browse/HBASE-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell closed HBASE-14401.
---------------------------------------

> 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: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 1.2.0, 1.3.0, 2.0.0
>
>         Attachments: 14401.txt, 14401.v7.txt, 14401.v7.txt, 14401.v7.txt, 14401v3.txt, 14401v3.txt, 14401v3.txt, 14401v6.txt
>
>
> 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
(v8.20.10#820010)