tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-214) Provide a way to debug Transaction Pruning progress
Date Tue, 07 Feb 2017 22:52:42 GMT

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

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

Github user gokulavasan commented on a diff in the pull request:

    https://github.com/apache/incubator-tephra/pull/31#discussion_r99951182
  
    --- Diff: tephra-hbase-compat-1.1-base/src/main/java/org/apache/tephra/hbase/txprune/HBaseTransactionPruningPlugin.java
---
    @@ -147,6 +147,7 @@ public long fetchPruneUpperBound(long time, long inactiveTransactionBound)
throw
     
         // Get all the current transactional regions
         SortedSet<byte[]> transactionalRegions = getTransactionalRegions();
    +    // TODO: Ignore empty
    --- End diff --
    
    That TODO was meant for ignoring empty regions from the current transactional regions.
I have removed that misleading TODO as part of the last commit.


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

Mime
View raw message