hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13013) Add read lock to ExpiredMobFileCleanerChore
Date Thu, 12 Feb 2015 16:54:11 GMT

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

Anoop Sam John commented on HBASE-13013:

Patch looks good
lock.acquire() might throw LockTimeoutException. Catch that specifically and avoid log error?
 Log info is enough for that case.

> 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.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

View raw message