hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingcheng Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16812) Clean up the locks in MOB
Date Thu, 26 Jan 2017 03:31:26 GMT

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

Jingcheng Du commented on HBASE-16812:

Thanks [~yuzhihong@gmail.com] for the comments.
bq. Can you clarify the above comment (for the case where delete marker does not have this
tag) ?
In this patch, the delete markers are not dropped anymore in the major compaction, and they
will live until they are expired.
As you know, in a major compaction, the del markers will be written to mob files. If we retain
the delete markers, they will be written to the mob files again and again. I add a tag for
the delete marker to avoid this. If a delete marker has such a tag, it is not flushed to mob
files again, and otherwise it is.
A new tag is not necessary? I am thinking of using the existing ref tag for the delete marker
to implement this. How do you think? Thanks.

> Clean up the locks in MOB
> -------------------------
>                 Key: HBASE-16812
>                 URL: https://issues.apache.org/jira/browse/HBASE-16812
>             Project: HBase
>          Issue Type: Task
>            Reporter: Appy
>            Assignee: Jingcheng Du
>            Priority: Minor
>         Attachments: HBASE-16812.master.001.patch, HBASE-16812.patch
> Clean up the locks in MOB. 
> # Retain all the delete markers in mob-enabled columns until they are expired.
> # Remove the locks from major compaction of mob-enabled columns.

This message was sent by Atlassian JIRA

View raw message