[jira] [Updated] (CASSANDRA-10929) cql_tests.py:AbortedQueriesTester fails

["Philip Thompson (JIRA)" <ji...@apache.org>]

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

Philip Thompson updated CASSANDRA-10929:
----------------------------------------
    Summary: cql_tests.py:AbortedQueriesTester fails  (was: cql_tests.py:AbortedQueriesTester.remote_query_test fails)

> cql_tests.py:AbortedQueriesTester fails
> ---------------------------------------
>
>                 Key: CASSANDRA-10929
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10929
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: CQL
>            Reporter: Philip Thompson
>             Fix For: 3.0.x, 3.x
>
>         Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log
>
>
> All four tests in the {{cql_tests.AbortedQueriesTester}} dtest suite are failing on HEAD of cassandra-3.0, here is an example link from cassci:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/455/testReport/cql_tests/AbortedQueriesTester/remote_query_test/
> The tests set {{'read_request_timeout_in_ms': 1000}}  and {{"-Dcassandra.test.read_iteration_delay_ms=1500"}}, then issues read queries and expects them to timeout. However, they are succeeding. I can reproduce this locally. 
> Looking at remote_query_test, from the logs, it appears that the query is being sent from the driver to node1, which forwards it to node2 appropriately. I've tried also setting {{range_request_timeout_in_ms}} lower, but that has had no effect. Trace logs from remote_query_test are attached.
> The same issue is happening on local_query_test, remote_query_test, materialized_view_test, and index_query_test.



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