[
https://issues.apache.org/jira/browse/HBASE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987256#comment-13987256
]
Matteo Bertozzi commented on HBASE-10926:
-----------------------------------------
{quote}Concurrent flush on the same table is rejected.{quote}
ok, you rely on the fact that coordinator.startProcedure() will return null
since the name is already used...
I don't see in the doc of ProcedureCoordinator anything that says that the
startProcedure() request is "rejected" if one with the same name is there, you
are relying on a current implementation detail, which sounds more an
implementation limitation than a feature that we wanted.
worth adding a comment in both places.
> 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)
