[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291450#comment-14291450
]
Lars Hofhansl commented on HBASE-12859:
---------------------------------------
No pain no gain :)
Cleanup or at least make it simpler to add stuff, definitely. Different jira...
It was just really frustrating to have to change all these things so they match
up, sorry I was really annoyed yesterday.
bq. What happens when master is down? Can it be ignored? It should be.
Should be all good, this patch adds add no new paradigm. ClusterStatus is
maintained by the master as before, the calls from HBaseAdmin to the master are
like the {{getClusterStatus()}} call; if master is down the calls with fail.
I think this fulfills all the requirements now:
* Master API to retrieve the last major compaction time.
* If one already has a ClusterStatus object one can derive it from there.
* HBaseAdmin convenience interface to get that information easily.
* Test that verifies the basic behavior and exercises all the new APIs.
* Piggy-backed on ClusterStatus, so no extra work or excessive roundtrips to
servers.
Good to commit? [~stack], [~apurtell], [~ghelmling].
I'd like to backport this all the way to 0.98.
> 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-v4.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)
