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-216) Invalid Transaction List Pruning will not proceed if there are empty transactional tables
Date Fri, 10 Feb 2017 08:31:41 GMT

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

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

GitHub user poornachandra opened a pull request:

    https://github.com/apache/incubator-tephra/pull/34

    TEPHRA-216 Handle empty transactional regions during inactive list pruning

    JIRA - https://issues.apache.org/jira/browse/TEPHRA-216
    
    Approach:
    1. Transaction Processor records a region as empty (at current time) in the post flush
handler if the memstore size for the region is zero and the region does not have any store
files.
    2. The regions that are recorded as empty after inactiveTransactionBoundTime will not
have invalid data for transactions started before or on inactiveTransactionBoundTime. Hence
we can consider the prune upper bound for these empty regions as the inactiveTransactionBound.
    
    TODO: Clean-up empty regions in pruneComplete()
    
    Note: The first two commits are re-factoring, and would be simple to review them separately.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/poornachandra/incubator-tephra feature/prune-empty-tables

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tephra/pull/34.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 #34
    
----
commit 2b796fa59c31c9003ede095d3c8c41b067a8142b
Author: poorna <poorna@cask.co>
Date:   2017-02-09T22:44:14Z

    Cleanup test and add warning in prune writer

commit 04e8a2207eead0d49e55539ed2b215958fadf6d3
Author: poorna <poorna@cask.co>
Date:   2017-02-10T01:07:30Z

    Refactor pruning plugin to handle empty regions

commit 73e1b83c4d937a409d4caf40715ab466b12253f1
Author: poorna <poorna@cask.co>
Date:   2017-02-10T08:18:13Z

    TEPHRA-216 Handle empty transactional regions during inactive list pruning

----


> Invalid Transaction List Pruning will not proceed if there are empty transactional tables
> -----------------------------------------------------------------------------------------
>
>                 Key: TEPHRA-216
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-216
>             Project: Tephra
>          Issue Type: Improvement
>    Affects Versions: 0.11.0-incubating
>            Reporter: Gokul Gunasekaran
>            Assignee: Poorna Chandra
>
> Since empty table/regions might not undergo major compaction, the prune upper bound of
these regions will never have a value and thus will limit the progress of invalid list transaction
pruning.



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

Mime
View raw message