[
https://issues.apache.org/jira/browse/HBASE-18905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-18905:
------------------------------
Release Note:
Add a FlushLifeCycleTracker which is similiar to CompactionLifeCycleTracker for
tracking flush.
Add a requestFlush method in Region interface to let CP users request flush on
a region. The operation is asynchronous, you need to use the
FlushLifeCycleTracker to track the flush.
The difference with CompactionLifeCycleTracker is that, flush is per region so
we do not use Store as a parameter of the methods. And also, notExecuted means
the whole flush has not been executed, and afterExecution means the whole flush
has been finished, so we do not have a separated completed method. A flush will
be ended either by notExecuted or afterExecution.
was:
dd a FlushLifeCycleTracker which is similiar to CompactionLifeCycleTracker for
tracking flush.
The difference with CompactionLifeCycleTracker is that, flush is per region so
we do not use Store as a parameter of the methods. And also, notExecuted means
the whole flush has not been executed, and afterExecution means the whole flush
has been finished, so we do not have a separated completed method. A flush will
be ended either by notExecuted or afterExecution.
> Allow CPs to request flush on Region and know the completion of the requested
> flush
> -----------------------------------------------------------------------------------
>
> Key: HBASE-18905
> URL: https://issues.apache.org/jira/browse/HBASE-18905
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Duo Zhang
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18905-addendum.patch, HBASE-18905-v1.patch,
> HBASE-18905.patch, HBASE-18905.patch
>
>
> Follow up for HBASE-18183
> As per that Jira, we keep only requestCompaction API in Region. We did not
> have any such for flush in Region. Only API which was there is a flush which
> will block the callee unless flush is done. This issue has to tacke
> 1. Decide whether we need a requestFlush in Region and if so add
> 2. Whether the requestCompaction (And requestFlush too) should return a
> Future? Right now the former do not return any but allow to pass a
> CompactionLifeCycleTracker which will get notified on start and end of
> compaction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
