[
https://issues.apache.org/jira/browse/HBASE-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279963#comment-14279963
]
Jingcheng Du commented on HBASE-12820:
--------------------------------------
Thanks Anoop [~anoopsamjohn].
Currently we use table locks in the major compaction of mob-enabled column,
sweeper and native mob compaction.
The major compactions of mob-enabled columns use read locks, and the other two
use write locks.
The write locks might block the usages other than mob, for instance the region
split, etc.
So is it ok to use a dummy table name for the table lock used in the mob? For
instance, use tableName + ".mobLock" as the dummy table name? Please advise.
Thanks.
> 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)
