[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983950#comment-13983950
]
Matteo Bertozzi commented on HBASE-10926:
-----------------------------------------
{quote}We don't need to have the agreement or consistency to flush across
region servers anyway. Any concern?{quote}
ok, I read the description of this jira. and what you really want is just
broadcasting a command to all the regions. not using a two-phase commit like
system.
If you look at HBASE-9864, there is some agreement to implement two
notification systems.
a two-phase commit one for broadcasting operations like grant/revoke on every
region server (the procedure),
and another one which is just a "state change" notification, which doesn't
require strong guarantees, which will probably be used by quotas as HBASE-11059.
since you have already done the patch, and all the code seems to be isolated in
procedure/flush i guess is fine if you just use acquireBarrier() to do the flush
> 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)
