[jira] [Updated] (CASSANDRA-9118) Validate that the Java driver and server don't generate timeouts in spuriously

2018-11-18 Thread C. Scott Andreas (JIRA)


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

C. Scott Andreas updated CASSANDRA-9118:

Component/s: Coordination

> 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
>  Components: Coordination
>Reporter: Ariel Weisberg
>Priority: Major
>
> 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
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-9118) Validate that the Java driver and server don't generate timeouts in spuriously

2015-04-03 Thread Ariel Weisberg (JIRA)

 [ 
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)