From dev-return-2135-archive-asf-public=cust-asf.ponee.io@tephra.incubator.apache.org Wed May 2 02:37:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D53BA180645 for ; Wed, 2 May 2018 02:37:03 +0200 (CEST) Received: (qmail 17677 invoked by uid 500); 2 May 2018 00:37:02 -0000 Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tephra.incubator.apache.org Delivered-To: mailing list dev@tephra.incubator.apache.org Received: (qmail 17666 invoked by uid 99); 2 May 2018 00:37:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2018 00:37:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6A2C5C7AB6 for ; Wed, 2 May 2018 00:37:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Ki2EDc7QqYeH for ; Wed, 2 May 2018 00:37:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 323B35F2C2 for ; Wed, 2 May 2018 00:37:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6B83EE0230 for ; Wed, 2 May 2018 00:37:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2AB9C21299 for ; Wed, 2 May 2018 00:37:00 +0000 (UTC) Date: Wed, 2 May 2018 00:37:00 +0000 (UTC) From: "Poorna Chandra (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TEPHRA-263) TTL is not strictly enforced, if there are long transactions running MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TEPHRA-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poorna Chandra updated TEPHRA-263: ---------------------------------- Fix Version/s: (was: 0.14.0-incubating) > TTL is not strictly enforced, if there are long transactions running > -------------------------------------------------------------------- > > Key: TEPHRA-263 > URL: https://issues.apache.org/jira/browse/TEPHRA-263 > Project: Tephra > Issue Type: Bug > Reporter: Ali Anwar > Assignee: Ali Anwar > Priority: Major > > The logic for filtering for TTL: > https://github.com/apache/incubator-tephra/blob/release/0.12.0-incubating/tephra-core/src/main/java/org/apache/tephra/util/TxUtils.java#L66 > It is subtracting the TTL duration from the visibility upper bound, but it should be subtracting from the current time or the current write pointer instead. Otherwise, if the TTL is 1 hour, but the visibility upper bound is 22 hours ago (due to some MR that has been in progress for 22 hours), then the TTL that is actually enforced will be 23 hours and older data will be filtered. > After the long transactions are invalidated, the TTL is then strictly enforced. -- This message was sent by Atlassian JIRA (v7.6.3#76005)