[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283132#comment-14283132
]
Lars Hofhansl commented on HBASE-12859:
---------------------------------------
bq. I'm not happy with either alternative.
Me neither.
bq. Con: Must contact each RS.
Yep. Can you believe that we're already doing that to get the compaction status
*every* time we show the table view in the UI?
So what about keeping just the HBaseAdmin API? Then we can vary the actual
implementation, and for now maybe keep the GetRegionInfo part since we're
already using the approach elsewhere. It also can't hurt to have this in
ClusterStatus.
> 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)
