[
https://issues.apache.org/jira/browse/HBASE-11114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993101#comment-13993101
]
Jonathan Hsieh commented on HBASE-11114:
----------------------------------------
The frame work should be compat.
I think we can go case by case with the commands that use it. Here are some
suggested rules:
1. old clients should be able to issue the command to new servers and new
clients should be able to issue to the command to old servers and still
succeed. Also, they should succeed in mixed old/new RS situations (e.g. while
we are doing a rolling upgrade).
2. I'm ok with having a flag for old behavior and all new clients in 0.98.x
default to old behavior. Switching to the new requires full shutdown/restart
unless #1 is met as well.
Let me give a more concrete example of a compat requirement for a global flush
method:
* 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).
* 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.)
> 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.3
>
>
> 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)
