[jira] [Commented] (HBASE-13013) Add read lock to ExpiredMobFileCleanerChore

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637814#comment-14637814 ] 

Hudson commented on HBASE-13013:
--------------------------------

FAILURE: Integrated in HBase-TRUNK #6672 (See [https://builds.apache.org/job/HBase-TRUNK/6672/])
HBASE-13013 - Add read lock to ExpiredMobFileCleanerChore (Jingcheng Du) (ramkrishna: rev 8f5dae471a9da95b144ecc15010028ba1ce7120c)
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/ExpiredMobFileCleanerChore.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/MobFileCompactionChore.java


> Add read lock to ExpiredMobFileCleanerChore
> -------------------------------------------
>
>                 Key: HBASE-13013
>                 URL: https://issues.apache.org/jira/browse/HBASE-13013
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>             Fix For: hbase-11339
>
>         Attachments: HBASE-13013-V2.diff, HBASE-13013.diff
>
>
> Now we have two chores for mob, one is the cleaner of expired mob files, the other is for the mob file compactor. They might handle the same file set concurrently, and might impact each other when doing that. We need to synchronize them, now we have a write lock for the mob file compaction chore, we need to add a read lock for the chore of expired mob file cleaner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)