You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2015/01/16 08:05:35 UTC
[jira] [Comment Edited] (HBASE-12820) Use table lock instead of
MobZookeeper
[ https://issues.apache.org/jira/browse/HBASE-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279897#comment-14279897 ]
Anoop Sam John edited comment on HBASE-12820 at 1/16/15 7:04 AM:
-----------------------------------------------------------------
TableLock is a broader one and we might delay other lock needed ops unwanted. This is my major concern.
Had some discussion with Jingcheng and some ways have come out.. He would add details.
Pls don't commit.
was (Author: anoop.hbase):
TableLock is a broader one and we might delay other lock needed ops unwanted. This is my major concern.
> Use table lock instead of MobZookeeper
> --------------------------------------
>
> Key: HBASE-12820
> URL: https://issues.apache.org/jira/browse/HBASE-12820
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Affects Versions: hbase-11339
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Fix For: hbase-11339
>
> Attachments: HBASE-12820-V2.diff, HBASE-12820-V3.diff, HBASE-12820-V4.diff, HBASE-12820.diff
>
>
> We had a lock to synchronize the major compaction, and sweep tool. Now we will have MR-less mob compaction in the HBase, and need the lock as well. And the table lock is a better choice. In this JIRA, clean the MobZookeeper code and use TableLockManager instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)