Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tephra.incubator.apache.org
Date: Mon, 11 Sep 2017 18:40:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@tephra.incubator.apache.org
Message-ID: <JIRA.13096227.1503161058000.81923.1505155200576@Atlassian.JIRA>
In-Reply-To: <JIRA.13096227.1503161058000@Atlassian.JIRA>
References: <JIRA.13096227.1503161058000@Atlassian.JIRA> <JIRA.13096227.1503161058046@jira-lw-us.apache.org>
Subject: [jira] [Commented] (TEPHRA-244) Invalid tx pruning does not handle
 deletion of tables well
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Sep 2017 18:40:07 -0000


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

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

Github user asfgit closed the pull request at:

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


> Invalid tx pruning does not handle deletion of tables well
> ----------------------------------------------------------
>
>                 Key: TEPHRA-244
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-244
>             Project: Tephra
>          Issue Type: Bug
>          Components: core, manager
>    Affects Versions: 0.12.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Poorna Chandra
>             Fix For: 0.13.0-incubating
>
>
> Suppose an application regularly creates and deletes tables (for example, temporary tables). In such a scenario, there will always be such a temporary table when pruning runs, and its regions will be recorded for that time. However, the region will be deleted before it ever compacts or flushes, and it will never record prune information. Because all prune times have such regions, there will never be a set of transactional regions that all have prune info, and pruning will never happen. 
> The fix is to exclude deleted tables from the list of regions at each time. This is all regions of deleted tables (tables that do not exist any more), not deleted regions: a region may disappear due to a split and its data will be in new regions. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)