You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/02/01 04:00:00 UTC

[jira] [Updated] (HBASE-21262) [hbck2] AMv2 Lock Picker

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

Guanghao Zhang updated HBASE-21262:
-----------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> [hbck2] AMv2 Lock Picker
> ------------------------
>
>                 Key: HBASE-21262
>                 URL: https://issues.apache.org/jira/browse/HBASE-21262
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hbck2, Operability
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>
> This issue is about adding a lock picker to the HbckService
> Over the w/e I had interesting case where an enable failed -- a subprocedure ran into an exclusive lock (I think) -- and then the parent enabletabled tried rollback. The rollback threw CODE-BUG because some subprocedures were in unrollbackable states.... so we ended up skipping out of the enable table procedure. The enable table procedure was marked ROLLBACKED... so it got GC'd. But the exclusive lock it had on the table stayed in place.
> The above has to be fixed but for the future, we need way to kill locks otherwise only alternative if removing master proc wal files -- which is a bigger pain restoring good state.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)