[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290926#comment-14290926
]
Lars Hofhansl commented on HBASE-12859:
---------------------------------------
I agree. It's fine to make master call after a compaction. (i.e. after we wrote
at least a memstore worth of data one RPC to the master won't cause an issue).
So for that it's indeed best to add a new master API (as [~apurtell] has said
all along), since we want to avoid (a) bringing all the cluster state over just
get compaction stats for a single region or table and (b) the need to contact
each an every region server (especially when we do this from another region
server).
> 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)
