Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 24 Oct 2017 19:53:00 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13105944.1506656717000.49521.1508874780461@Atlassian.JIRA>
In-Reply-To: <JIRA.13105944.1506656717000@Atlassian.JIRA>
References: <JIRA.13105944.1506656717000@Atlassian.JIRA> <JIRA.13105944.1506656717465@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-18905) Allow CPs to request flush on
 Region and know the completion of the requested flush
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 Oct 2017 19:53:05 -0000


    [ https://issues.apache.org/jira/browse/HBASE-18905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217571#comment-16217571 ] 

stack commented on HBASE-18905:
-------------------------------

bq. Just want to follow the other methods below, beforeExecution and afterExecution. And the word 'fail' may give users an impression that something serious is happened, but here it usually only means that there is already a flush ongoing.

Ok.

> 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.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)