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 4452C2004A0 for ; Wed, 16 Aug 2017 22:00:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 42AE516982E; Wed, 16 Aug 2017 20:00:15 +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 8AC7416982D for ; Wed, 16 Aug 2017 22:00:14 +0200 (CEST) Received: (qmail 31931 invoked by uid 500); 16 Aug 2017 20:00:12 -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 31920 invoked by uid 99); 16 Aug 2017 20:00:12 -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; Wed, 16 Aug 2017 20:00:12 +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 671051A19E3 for ; Wed, 16 Aug 2017 20:00:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 LNrwkzRqxVJ5 for ; Wed, 16 Aug 2017 20:00:11 +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 0754F5FB8D for ; Wed, 16 Aug 2017 20:00:11 +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 D771FE0114 for ; Wed, 16 Aug 2017 20:00:09 +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 1701A25386 for ; Wed, 16 Aug 2017 20:00:08 +0000 (UTC) Date: Wed, 16 Aug 2017 20:00:08 +0000 (UTC) From: "Andreas Neumann (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TEPHRA-240) TransactionConflictException should contain the conflicting key and client id MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 16 Aug 2017 20:00:15 -0000 [ https://issues.apache.org/jira/browse/TEPHRA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129328#comment-16129328 ] Andreas Neumann commented on TEPHRA-240: ---------------------------------------- Currently, we do not keep the client id after the transaction commits. The change set that is kept for conflict detection is not labeled with the client id. Adding that is easy but may increase the memory footprint. Therefore, there should be an configuration option whether this should be kept or not. Also, because the client id is only in memory but not persisted to the transaction snapshot, this info will not be available after a restart. > TransactionConflictException should contain the conflicting key and client id > ----------------------------------------------------------------------------- > > Key: TEPHRA-240 > URL: https://issues.apache.org/jira/browse/TEPHRA-240 > Project: Tephra > Issue Type: Bug > Reporter: Andreas Neumann > Assignee: Poorna Chandra > > Often transaction conflicts are hard to explain. Having the conflicting key, or even the name of the client that performed the concurrent update would greatly help debug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)