[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290922#comment-14290922
]
Andrew Purtell commented on HBASE-12859:
----------------------------------------
We used to track region state in the meta table, updated inline with actions
like splitting. It was for the Region Historian feature and was a source of
deadlocks and downtime whenever there was a network issue or inopportune region
relocation or node failure. We ripped it out a long time ago.
If this API is going to be called from a region observer I think this
prescribes a master API so there is only one RPC to one location necessary to
retrieve the information needed, quickly. We have various options for how the
master might collect and provide the information.
> 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
(v6.3.4#6332)
