cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-10730) periodic timeout errors in dtest
Date Wed, 18 Nov 2015 16:46:10 GMT
Jim Witschey created CASSANDRA-10730:
----------------------------------------

             Summary: periodic timeout errors in dtest
                 Key: CASSANDRA-10730
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10730
             Project: Cassandra
          Issue Type: Bug
            Reporter: Jim Witschey
            Assignee: Jim Witschey


Dtests often fail with connection timeout errors. For example:

http://cassci.datastax.com/job/cassandra-3.1_dtest/lastCompletedBuild/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3/deletion_test/

{code}
('Unable to connect to any servers', {'127.0.0.1': OperationTimedOut('errors=Timed out creating
connection (10 seconds), last_host=None',)})
{code}

We've merged a PR to increase timeouts:

https://github.com/riptano/cassandra-dtest/pull/663

It doesn't look like this has improved things:

http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/363/testReport/

Next steps here are

* to scrape Jenkins history to see if and how the number of tests failing this way has increased
(it feels like it has). From there we can bisect over the dtests, ccm, or C*, depending on
what looks like the source of the problem.
* to better instrument the dtest/ccm/C* startup process to see why the nodes start but don't
successfully make the CQL port available.



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

Mime
View raw message