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 4D486200D6A for ; Sat, 16 Dec 2017 01:48:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4B483160C26; Sat, 16 Dec 2017 00:48:04 +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 90BF3160C14 for ; Sat, 16 Dec 2017 01:48:03 +0100 (CET) Received: (qmail 60958 invoked by uid 500); 16 Dec 2017 00:48: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 60947 invoked by uid 99); 16 Dec 2017 00:48:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Dec 2017 00:48:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 60FF51A075F for ; Sat, 16 Dec 2017 00:48:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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=[RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ZOeH8nTcjePF for ; Sat, 16 Dec 2017 00:48: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 128835F2A8 for ; Sat, 16 Dec 2017 00:48: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 55F0FE00A3 for ; Sat, 16 Dec 2017 00:48: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 12AA427401 for ; Sat, 16 Dec 2017 00:48:00 +0000 (UTC) Date: Sat, 16 Dec 2017 00:48:00 +0000 (UTC) From: "Poorna Chandra (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (TEPHRA-271) Stopping transaction state cache should wait for the refresh thread to stop MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 16 Dec 2017 00:48:04 -0000 Poorna Chandra created TEPHRA-271: ------------------------------------- Summary: Stopping transaction state cache should wait for the refresh thread to stop Key: TEPHRA-271 URL: https://issues.apache.org/jira/browse/TEPHRA-271 Project: Tephra Issue Type: Improvement Components: core Reporter: Poorna Chandra Assignee: Poorna Chandra Fix For: 0.14.0-incubating Transaction state cache has a background thread that refreshes transaction snapshots every now and then. This thread is started when transaction state cache is started, and stopped when transaction state cache is stopped. However, the stop does not wait for the thread to completely stop before returning. This can lead to race conditions when the calling code expects the thread to be completely stopped when transaction state cache is stopped. -- This message was sent by Atlassian JIRA (v6.4.14#64029)