Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 14 Jan 2016 21:08:39 +0000 (UTC)
From: "Jim Witschey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12914164.1447865126000.114395.1452805719938@Atlassian.JIRA>
In-Reply-To: <JIRA.12914164.1447865126000@Atlassian.JIRA>
References: <JIRA.12914164.1447865126000@Atlassian.JIRA>
 <JIRA.12914164.1447865126028@arcas>
Subject: [jira] [Commented] (CASSANDRA-10730) periodic timeout errors in
 dtest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098860#comment-15098860 ] 

Jim Witschey commented on CASSANDRA-10730:
------------------------------------------

This class of error has stopped happening. There are still some tests that flap when nodes are unavailable, but the problem is unrelated, as described in CASSANDRA-11016. If anyone thinks I'm wrong, feel free to reopen or open a new ticket, but I'm closing.

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