[jira] [Commented] (HBASE-11114) Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98
[ https://issues.apache.org/jira/browse/HBASE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005527#comment-14005527 ] Jerry He commented on HBASE-4: -- 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-4 URL: https://issues.apache.org/jira/browse/HBASE-4 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)
[jira] [Commented] (HBASE-11114) Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98
[ https://issues.apache.org/jira/browse/HBASE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998654#comment-13998654 ] Andrew Purtell commented on HBASE-4: Sounds good Jon. Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98 - Key: HBASE-4 URL: https://issues.apache.org/jira/browse/HBASE-4 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)
[jira] [Commented] (HBASE-11114) Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98
[ https://issues.apache.org/jira/browse/HBASE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993101#comment-13993101 ] Jonathan Hsieh commented on HBASE-4: 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-4 URL: https://issues.apache.org/jira/browse/HBASE-4 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)
[jira] [Commented] (HBASE-11114) Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98
[ https://issues.apache.org/jira/browse/HBASE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13989075#comment-13989075 ] Andrew Purtell commented on HBASE-4: The coprocessor API changes in the committed patch for HBASE-4 add methods only, so would be ok to port back. I think the procedure framework in 0.98 can support the changes also. I think the one question is if the flush behavior change is ok to make from one minor release to another. In my opinion we should take a liberal attitude to changes that improve efficiency without changing client facing API, and when security is active flushing is a restricted activity already. A release note should be sufficient. Backport HBASE-10926 (Use global procedure to flush table memstore cache) to 0.98 - Key: HBASE-4 URL: https://issues.apache.org/jira/browse/HBASE-4 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)
