[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030246#comment-14030246
]
Jerry He commented on HBASE-10926:
----------------------------------
bq. WARN [main-EventThread] procedure.ProcedureMember: A completed old subproc
cluster_test is still present, removing
This one seems to be normal and expected. That is the only way to normally
remove a completed subproc from the list.
bq. WARN [main-EventThread] procedure.ProcedureCoordinator: Member
'cluster_test' is trying to release an unknown procedure 'reached'
This one is puzzling. It comes from this part in the code:
{code}
void memberFinishedBarrier(String procName, final String member, byte[]
dataFromMember) {
Procedure proc = procedures.get(procName);
if (proc == null) {
LOG.warn("Member '"+ member +"' is trying to release an unknown procedure
'"+ procName +"'");
return;
}
proc.barrierReleasedByMember(member, dataFromMember);
}
{code}
'cluster_test' should be the proc name.
Are there any errors/exceptions or procedure timeout in the output?
> 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)
