[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987174#comment-13987174
]
Matteo Bertozzi commented on HBASE-10926:
-----------------------------------------
You now have the procMap used for isProcedureDone() but you don't reject
concurrent flush on the same table, is that on purpose?
There is a missing T in FLUSH_IMEOUT_MILLIS_KEY and I guess the timeout conf is
a little bit tricky (I know that you have followed the snapshots). In theory
the timeout master should be > than the rs timeout, but you are using the
default procedure timeout, so the conf on the rs is "not considered" in case
you want to bump that up.
all the other stuff looks ok to me
> 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, HBASE-10926-trunk-v2.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)
