[
https://issues.apache.org/jira/browse/TEPHRA-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891325#comment-15891325
]
ASF GitHub Bot commented on TEPHRA-227:
---------------------------------------
GitHub user gokulavasan opened a pull request:
https://github.com/apache/incubator-tephra/pull/40
TEPHRA-227 Add a new command to get the set of regions that have not been
compacted
Also adding a CLI command.
JIRA : https://issues.apache.org/jira/browse/TEPHRA-227
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gokulavasan/incubator-tephra fix/tephra-227
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tephra/pull/40.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #40
----
commit c2b76408facb5d9b8169876c7830ec08759da455
Author: Gokul Gunasekaran <[email protected]>
Date: 2017-03-01T22:54:40Z
(TEPHRA-227) Add new command to get the set of regions that have not been
compacted
commit 7111ce76e19ed1be012e5a5d7f11b30e8dc757c2
Author: Gokul Gunasekaran <[email protected]>
Date: 2017-03-01T23:49:26Z
Adding CLI command for the new getRegionsToBeCompacted method
----
> 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)
