hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12859) Major compaction completion tracker
Date Sun, 25 Jan 2015 00:48:35 GMT

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

James Taylor commented on HBASE-12859:

Is there such a thing as per region metadata? If not, that would be a useful feature. On a
split, it could duplicate the metadata and on a merge combine it. For any region re-assignment,
the metadata would follow.

For PHOENIX-1590, in the preCompact region observer, we'd need to query the SYSTEM.CATALOG
to get the information to build the filter, so we'd potentially be going to another region
server. For secondary indexing, we solved the potential for deadlock issue by using a high
priority queue for index updates. Maybe the same could be done here?

> Major compaction completion tracker
> -----------------------------------
>                 Key: HBASE-12859
>                 URL: https://issues.apache.org/jira/browse/HBASE-12859
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
>         Attachments: 12859-v1.txt, 12859-v2.txt, 12859-v3.txt, 12859-wip-UNFINISHED.txt
> In various scenarios it is helpful to know a guaranteed timestamp up to which all data
in a table was major compacted.
> We can do that keeping a major compaction timestamp in META.
> A client then can iterate all region of a table and find a definite timestamp, which
is the oldest compaction timestamp of any of the regions.
> [~apurtell], [~ghelmling], [~giacomotaylor].

This message was sent by Atlassian JIRA

View raw message