Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tephra.incubator.apache.org
Date: Thu, 7 Jul 2016 08:42:10 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: dev@tephra.incubator.apache.org
Message-ID: <JIRA.12982973.1409263454000.46304.1467880930974@Atlassian.JIRA>
In-Reply-To: <JIRA.12982973.1409263454000@Atlassian.JIRA>
References: <JIRA.12982973.1409263454000@Atlassian.JIRA> <JIRA.12982973.1409263454000@arcas>
Subject: [jira] [Commented] (TEPHRA-35) Prune invalid transaction set once
 all data for a given invalid transaction has been dropped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Jul 2016 08:42:18 -0000


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

James Taylor commented on TEPHRA-35:
------------------------------------

I still think putting the burden at the application level to either track which tables are involved in a transaction or waiting until every single table has been major compacted is too high. Why can't the client send the table names over when a commit occurs? Then, only in the exception case of a client not being able to reach the transaction manager would it be required that all transactional tables be major compacted. Or maybe some other alternative? How does Omid deal with this?

> Prune invalid transaction set once all data for a given invalid transaction has been dropped
> --------------------------------------------------------------------------------------------
>
>                 Key: TEPHRA-35
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-35
>             Project: Tephra
>          Issue Type: New Feature
>            Reporter: Gary Helmling
>            Assignee: Poorna Chandra
>            Priority: Blocker
>         Attachments: ApacheTephraAutomaticInvalidListPruning-v2.pdf
>
>
> In addition to dropping the data from invalid transactions we need to be able to prune the invalid set of any transactions where data cleanup has been completely performed. Without this, the invalid set will grow indefinitely and become a greater and greater cost to in-progress transactions over time.
> To do this correctly, the TransactionDataJanitor coprocessor will need to maintain some bookkeeping for the transaction data that it removes, so that the transaction manager can reason about when all of a given transaction's data has been removed. Only at this point can the transaction manager safely drop the transaction ID from the invalid set.
> One approach would be for the TransactionDataJanitor to update a table marking when a major compaction was performed on a region and what transaction IDs were filtered out. Once all regions in a table containing the transaction data have been compacted, we can remove the filtered out transaction IDs from the invalid set. However, this will need to cope with changing region names due to splits, etc.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)