Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 19 Oct 2016 00:35:59 +0000 (UTC)
From: "Jeff Jirsa (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13004080.1473520930000.23559.1476837359891@Atlassian.JIRA>
In-Reply-To: <JIRA.13004080.1473520930000@Atlassian.JIRA>
References: <JIRA.13004080.1473520930000@Atlassian.JIRA> <JIRA.13004080.1473520930967@arcas>
Subject: [jira] [Updated] (CASSANDRA-12626) LWT contention appears to be
 under reported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 19 Oct 2016 00:36:01 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Jirsa updated CASSANDRA-12626:
-----------------------------------
    Fix Version/s:     (was: 3.x)
                   3.10

> LWT contention appears to be under reported
> -------------------------------------------
>
>                 Key: CASSANDRA-12626
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12626
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability
>            Reporter: Christopher Batey
>            Assignee: Christopher Batey
>            Priority: Minor
>             Fix For: 3.10
>
>
> I was surprised how little contention was being reported and looking at the code we miss out reporting contention when there is a timeout at the prepare phase.
> If this {{StorageProxy.beginAndRepairPaxos}} throws then the contentions count isn't added to the histogram.


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