hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-5494) Introduce a zk hosted table-wide read/write lock so only one table operation at a time
Date Sat, 12 May 2012 04:19:49 GMT

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

stack resolved HBASE-5494.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.89-fb
         Assignee: Alex Feinberg
     Hadoop Flags: Reviewed

Alex's patch committed to 0.89fb.  Thanks for the patch Alex (added you as hbase contributor
and assigned you this issue).  We'll do up a trunk version of this patch over in HBASE-5991
where we base it on read/write zk locks.
                
> 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: stack
>            Assignee: Alex Feinberg
>             Fix For: 0.89-fb
>
>         Attachments: D2997.3.patch, D2997.4.patch, D2997.5.patch, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message