You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tephra.apache.org by "Poorna Chandra (JIRA)" <ji...@apache.org> on 2017/02/22 22:50:44 UTC
[jira] [Resolved] (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:all-tabpanel ]
Poorna Chandra resolved TEPHRA-224.
-----------------------------------
Resolution: Fixed
> 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.11.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)