Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 5 Oct 2016 08:45:20 +0000 (UTC)
From: "Stefania (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13009153.1475462984000.740337.1475657120562@Atlassian.JIRA>
In-Reply-To: <JIRA.13009153.1475462984000@Atlassian.JIRA>
References: <JIRA.13009153.1475462984000@Atlassian.JIRA> <JIRA.13009153.1475462984127@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-12740) cqlsh copy tests hang in
 case of no answer from the server or driver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 05 Oct 2016 08:45:22 -0000


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

Stefania edited comment on CASSANDRA-12740 at 10/5/16 8:44 AM:
---------------------------------------------------------------

3.0 tests look clean, launching tests for other branches and moving to patch available.


was (Author: stefania):
3.0 tests look clean, launching tests to other branches and moving to patch available.

> cqlsh copy tests hang in case of no answer from the server or driver
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-12740
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12740
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>
> -If we bundle the driver to cqlsh using the 3.6.0 tag or cassandra_test head, some cqlsh copy tests hang, for example {{test_bulk_round_trip_blogposts}}. See CASSANDRA-12736 and CASSANDRA-11534 for some sample failures.-
> If the driver fails to invoke a callback (either error or success), or if the server never answers to the driver, then the copy parent process will wait forever to receive an answer from child processes. We should put a cap to this. We should also use a very high timeout rather than None, so that the driver will notify us if there is no answer from the server.


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