[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029777#comment-14029777
]
Andrew Purtell commented on HBASE-10926:
----------------------------------------
I started a minicluster based instance of recent trunk and ran LoadTestTool
concurrent with flushing every 10 seconds, to generate a lot of HFiles. In the
logs I notice a lot of Procedure related WARNs:
122 of these logged over 30 minutes:
bq. WARN [main-EventThread] procedure.ProcedureCoordinator: Member
'cluster_test' is trying to release an unknown procedure 'reached'
112 of these logged over 30 minutes:
bq. WARN [main-EventThread] procedure.ProcedureMember: A completed old subproc
cluster_test is still present, removing
Given the rate at which I was triggering flushes, there would have been ~180
procedure executions, meaning we had these warnings 67% of the time. At a
minimum this is noisy WARN level logging.
> 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)
