[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983931#comment-13983931
]
Jerry He commented on HBASE-10926:
----------------------------------
bq. The behavior change more is related to the failure case, if a RS is
not-responding with the procedure you fail the flush, while with the old method
some of them got flushed.
Regarding this behavior, if I put the flush region tasks in 'acquireBarrier'
phase, not the 'insideBarrier' phase, it will probably help somehow to maintain
the old behavior.
We don't need to have the agreement or consistency to flush across region
servers anyway.
Any concern?
> Use global procedure to flush table memstore cache
> --------------------------------------------------
>
> Key: HBASE-10926
> URL: https://issues.apache.org/jira/browse/HBASE-10926
> Project: HBase
> Issue Type: Improvement
> Components: Admin
> Affects Versions: 0.96.2, 0.98.1
> Reporter: Jerry He
> Assignee: Jerry He
> Fix For: 0.99.0
>
> Attachments: HBASE-10926-trunk-v1.patch
>
>
> 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)
