Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 3 Apr 2015 21:29:52 +0000 (UTC)
From: "Ariel Weisberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12788111.1428096340000.121669.1428096592727@Atlassian.JIRA>
In-Reply-To: <JIRA.12788111.1428096340000@Atlassian.JIRA>
References: <JIRA.12788111.1428096340000@Atlassian.JIRA>
 <JIRA.12788111.1428096340273@arcas>
Subject: [jira] [Updated] (CASSANDRA-9118) Validate that the Java driver and
 server don't generate timeouts in spuriously
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ariel Weisberg updated CASSANDRA-9118:
--------------------------------------
    Issue Type: Sub-task  (was: Test)
        Parent: CASSANDRA-9007

> Validate that the Java driver and server don't generate timeouts in spuriously
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9118
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9118
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Ariel Weisberg
>
> Inspired by the alleged regression CASSANDRA-9023.
> It's understandable that during validation there will be timeouts, but for some period we should create a scenario where we know there really shouldn't be timeouts, and then error if there are. The goal is to make sure that if the driver or server is generating timeouts that they are for legitimate reasons.
> Unless someone wants to make the argument there there is no scenario under which timeouts are not expected.


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