[jira] [Closed] (HBASE-5494) Introduce a zk hosted table-wide read/write lock so only one table operation at a time

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

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

Andrew Kyle Purtell closed HBASE-5494.
--------------------------------------

> Introduce a zk hosted table-wide read/write lock so only one table operation at a time
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-5494
>                 URL: https://issues.apache.org/jira/browse/HBASE-5494
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Michael Stack
>            Assignee: Alex Feinberg
>            Priority: Major
>             Fix For: 0.89-fb
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--D2997.3.patch, ASF.LICENSE.NOT.GRANTED--D2997.4.patch, ASF.LICENSE.NOT.GRANTED--D2997.5.patch, ASF.LICENSE.NOT.GRANTED--D2997.6.patch
>
>
> I saw this facility over in the accumulo code base.
> Currently we just try to sort out the mess when splits come in during an online schema edit; somehow we figure we can figure all possible region transition combinations and make the right call.
> We could try and narrow the number of combinations by taking out a zk table lock when doing table operations.
> For example, on split or merge, we could take a read-only lock meaning the table can't be disabled while these are running.
> We could then take a write only lock if we want to ensure the table doesn't change while disabling or enabling process is happening.
> Shouldn't be too hard to add.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)