[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983274#comment-13983274
]
Ted Yu commented on HBASE-10926:
--------------------------------
{code}
[email protected]
[email protected]
+public class FlushTableSubprocedure extends Subprocedure {
{code}
Private implies Unstable.
{code}
+ // Using the completion service to process the futures that finish
first first.
{code}
'first' was repeated.
{code}
+ Future<Void> f = taskPool.take();
+ f.get();
{code}
You may want to add timeout for the get() call.
> 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)
