[
https://issues.apache.org/jira/browse/HBASE-11114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005527#comment-14005527
]
Jerry He commented on HBASE-11114:
----------------------------------
bq. Old HBaseAdmin clients (say 0.98.0) who use the old style global flush
should be able to issue the commands to newer servers (0.98.3 let's say).
This should work fine if we backport directly. Old client will still go to
region servers to flush without involving the global procedure.
bq. New HBaseAdmin clients (say 0.98.3) could try to do the new style flush to
old servers (0.98.00 but should fall back to the old style if it is rejected
with some sort of not supported error.)
This will break.
> Backport HBASE-10926 (Use global procedure to flush table memstore cache) to
> 0.98
> ---------------------------------------------------------------------------------
>
> Key: HBASE-11114
> URL: https://issues.apache.org/jira/browse/HBASE-11114
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.98.4
>
>
> Backport HBASE-10926 to 0.98.
> Description from original issue: Currently, user can trigger table flush
> through hbase shell or HBaseAdmin API. To flush the table cache, each region
> server hosting the regions is contacted and flushed sequentially, which is
> less efficient. In HBase snapshot global procedure is used to coordinate and
> flush the regions in a distributed way. Let's provide a distributed table
> flush for general use.
--
This message was sent by Atlassian JIRA
(v6.2#6252)