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/03/07 17:19:38 UTC

[jira] [Updated] (TEPHRA-225) Clean up prune state when invalid list is empty

     [ https://issues.apache.org/jira/browse/TEPHRA-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Poorna Chandra updated TEPHRA-225:
----------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: TEPHRA-35)

> Clean up prune state when invalid list is empty
> -----------------------------------------------
>
>                 Key: TEPHRA-225
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-225
>             Project: Tephra
>          Issue Type: Improvement
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>             Fix For: 0.12.0-incubating
>
>
> Invalid list can be empty in two cases - when transaction manager just starts up, or when all invalid transaction ids get pruned. When a prune run starts with empty invalid list, then we can clean up prune state using the inactive transaction bound, since there can be no data from an invalid transaction smaller than the inactive transaction bound in the store. Hence we don't need any prune state that is stored earlier than the inactive transaction bound.



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