[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291178#comment-14291178
]
stack commented on HBASE-12859:
-------------------------------
What happens when master is down? Can it be ignored? It should be.
bq. W.......T.......F....... have we done? It takes 10 mins to make the change
and then 2h to work through the protobuf rabbithole. MEH.
The pb convertion was done by multiple people at various times.
ProtobufUtil + RequestConverter + ResponseConverter have overlap. Should just
have a pure pbutil and bulk of pbutil should be moved to RequestConverter and
ResponseConverter or the latter two should just be removed.
MasterServices has nought to do w/ pb. It is backfill of a Master Interface.
MasterRpcServices ditto. It is an after-the-fact attempt at slimming down
Master moving out initial rpc handling to a dedicated class.
MasterServices.BlockingInterface is from pb. Thats how the rpc Interface stubs
are one.
Sorry its a pain. Could do w/ cleanup yep.
> 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)
