You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tephra.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/22 01:16:44 UTC

[jira] [Commented] (TEPHRA-224) Handle delay between transaction max lifetime check and data writes while pruning

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

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

GitHub user poornachandra opened a pull request:

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

    TEPHRA-224 Handle delay between transaction max lifetime check and data writes while pruning

    JIRA - https://issues.apache.org/jira/browse/TEPHRA-224

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

    $ git pull https://github.com/poornachandra/incubator-tephra feature/pruning-buffer

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

    https://github.com/apache/incubator-tephra/pull/38.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 #38
    
----

----


> Handle delay between transaction max lifetime check and data writes while pruning
> ---------------------------------------------------------------------------------
>
>                 Key: TEPHRA-224
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-224
>             Project: Tephra
>          Issue Type: Sub-task
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>             Fix For: 0.12.0-incubating
>
>
> Transaction pruning relies on inactive transaction bound (a bound that says at a given time there will be no transactions smaller than inactive transaction bound that can still be writing data). To determine the inactive transaction bound for a given time, TEPHRA-199 introduced transaction maximum lifetime.
> However there can be a delay between the transaction max lifetime being enforced and the write reaching HBase. Hence it would be good to use a buffer to pad the transaction max lifetime when pruning.



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