stack commented on HBASE-20847:

+1 on v3. I like explanation in releaseExclusiveLock.

On backport to branch-2.0, I'm worried there'll be side-effects and that we 
need more than this fix. Let me make a separate issue for backport to 
branch-2.0. Will evaluate before pushing a 2.0.2. I can do it.

> The parent procedure of RegionTransitionProcedure may not have the table lock
> -----------------------------------------------------------------------------
>                 Key: HBASE-20847
>                 URL: https://issues.apache.org/jira/browse/HBASE-20847
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2, Region Assignment
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>         Attachments: HBASE-20847-addendum.patch, 
> HBASE-20847-branch-2.0-v1.patch, HBASE-20847-branch-2.0.patch, 
> HBASE-20847-v1.patch, HBASE-20847-v2.patch, HBASE-20847-v3.patch, 
> HBASE-20847.patch
> For example, SCP can also schedule AssignProcedure and obviously it will not 
> hold the table lock.

This message was sent by Atlassian JIRA

Reply via email to