Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tephra.incubator.apache.org
Date: Fri, 3 Mar 2017 01:48:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@tephra.incubator.apache.org
Message-ID: <JIRA.13047499.1488408266000.50207.1488505725594@Atlassian.JIRA>
In-Reply-To: <JIRA.13047499.1488408266000@Atlassian.JIRA>
References: <JIRA.13047499.1488408266000@Atlassian.JIRA> <JIRA.13047499.1488408266259@jira-lw-us.apache.org>
Subject: [jira] [Commented] (TEPHRA-227) DebugTool - show regions that have
 not yet recorded prune upper bound
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 03 Mar 2017 01:48:51 -0000


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

ASF GitHub Bot commented on TEPHRA-227:
---------------------------------------

Github user poornachandra commented on the issue:

    https://github.com/apache/incubator-tephra/pull/40
  
    LGTM


> DebugTool - show regions that have not yet recorded prune upper bound 
> ----------------------------------------------------------------------
>
>                 Key: TEPHRA-227
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-227
>             Project: Tephra
>          Issue Type: Improvement
>    Affects Versions: 0.11.0-incubating
>            Reporter: Gokul Gunasekaran
>            Assignee: Poorna Chandra
>             Fix For: 0.11.0-incubating
>
>
> i) getIdleRegions (numRegions) --> since this method returns all the regions that have ever existed, this is not very useful since some regions might not be existing anymore. So, we need to intersect the idleregions with the latest TimeRegion regions.
> ii) add a new method - getRegionsToBeFlushed ( ) --> that returns the regions that are part of the latest TimeRegion but don't have any prune upper bound recorded and or not empty either.
> So during debugging of prune progress, first we can hit the second method and get the regions to be flushed/compacted (since any regions that have not compacted/pruned will prevent pruning from progression). After that list is empty, we will hit the first endpoint to find what regions are lagging, pruning/compacting them will help advance pruning.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)