[
https://issues.apache.org/jira/browse/TEPHRA-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855286#comment-15855286
]
ASF GitHub Bot commented on TEPHRA-214:
---------------------------------------
GitHub user gokulavasan opened a pull request:
https://github.com/apache/incubator-tephra/pull/31
(TEPHRA-214) Tool to debug the state and progress of Invalid List Pruning
JIRA : https://issues.apache.org/jira/browse/TEPHRA-214
Summary: Introduce a debug tool to fetch data that might help with
debugging the status and progress of invalid list transaction list pruning.
Three commands are supported:
timeregion <timestamp> ==> Will return TimeRegions at or before timestamp
in millis
idleregions <numOfRegions> ==> Will return numOfRegions regions with lowest
pruneUpperBounds. If -1 is provided, all pruneUpperBounds are returned.
pruneinfo <regionNameAsString> => Will return pruneUpperBound,
compactionTimeStamp of the 'regionNameAsString' region.
This tool can be invoked with hbase classpath and tephra jars in the
classpath.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gokulavasan/incubator-tephra
feature/tephra-pruning-debug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tephra/pull/31.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 #31
----
commit dc4357824e8e48973cc5109c649aa8303f077233
Author: Gokul Gunasekaran <go...@cask.co>
Date: 2017-02-03T20:10:40Z
(TEPHRA-214) Tool to debug the state and progress of Invalid List Pruning
----
> Provide a way to debug Transaction Pruning progress
> ---------------------------------------------------
>
> Key: TEPHRA-214
> URL: https://issues.apache.org/jira/browse/TEPHRA-214
> Project: Tephra
> Issue Type: Improvement
> Reporter: Gokul Gunasekaran
> Assignee: Gokul Gunasekaran
>
> It would be good to get information about what regions are lagging that might
> be useful to debug why transaction pruning might not be happening. We do
> print debug information but this method could be invoked on a need-basis
> outside of the regular pruning operation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
