Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B07D6200D02 for ; Fri, 8 Sep 2017 23:08:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AECD31609C1; Fri, 8 Sep 2017 21:08:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 095C01609D7 for ; Fri, 8 Sep 2017 23:08:05 +0200 (CEST) Received: (qmail 35235 invoked by uid 500); 8 Sep 2017 21:08:04 -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 35221 invoked by uid 99); 8 Sep 2017 21:08:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2017 21:08:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 63CCB1916B6 for ; Fri, 8 Sep 2017 21:08:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id on3T5wDj-4JQ for ; Fri, 8 Sep 2017 21:08:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7D3875FCB9 for ; Fri, 8 Sep 2017 21:08:03 +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 D3189E0E66 for ; Fri, 8 Sep 2017 21:08:01 +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 F3B532416A for ; Fri, 8 Sep 2017 21:08:00 +0000 (UTC) Date: Fri, 8 Sep 2017 21:08:00 +0000 (UTC) From: "Andreas Neumann (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (TEPHRA-250) Create a way to trigger transaction pruning MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Sep 2017 21:08:06 -0000 [ https://issues.apache.org/jira/browse/TEPHRA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann reassigned TEPHRA-250: -------------------------------------- Assignee: Andreas Neumann (was: Poorna Chandra) > Create a way to trigger transaction pruning > -------------------------------------------- > > Key: TEPHRA-250 > URL: https://issues.apache.org/jira/browse/TEPHRA-250 > Project: Tephra > Issue Type: Improvement > Components: core, manager > Affects Versions: 0.12.0-incubating > Reporter: Andreas Neumann > Assignee: Andreas Neumann > Fix For: 0.13.0-incubating > > > Currently, pruning can be configured to run at a certain frequency, say every hour. But especially when pruning does not work well, and one tries various things to address that, it is very tedious to have to wait for the next scheduled pruning run. It would be good to be able to trigger it immediately after a change was made, to see whether that change helped. -- This message was sent by Atlassian JIRA (v6.4.14#64029)