[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029882#comment-14029882
]
Matteo Bertozzi commented on HBASE-10926:
-----------------------------------------
The warn means that someone joined the procedure "later", which in this case is
not really a problem.
but more in general it is part of the problem described in HBASE-11221. once
the procedure start it is not aware of the new server joining or regions
moving. I'm working on a patch, but I'm stuck in finding a way to make it
compatible for a rolling restart.
> 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,
> HBASE-10926-trunk-v3.patch, HBASE-10926-trunk-v4.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)
