You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/05/04 20:11:14 UTC

[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-11114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989075#comment-13989075 ] 

Andrew Purtell commented on HBASE-11114:
----------------------------------------

The coprocessor API changes in the committed patch for HBASE-11114 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-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)