cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11157) test_bulk_round_trip_blogposts_with_max_connections got "Truncate timed out"
Date Thu, 11 Feb 2016 06:05:18 GMT

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

Stefania commented on CASSANDRA-11157:
--------------------------------------

Actually the error originates server side and the timeout is controlled by the yaml property
{{truncate_request_timeout_in_ms}} which by default is 60 seconds but it is set to 10 seconds
by _dtest.py_ {{init_default_config()}}.

I propose to use 60 seconds for bulk copy tests.

> test_bulk_round_trip_blogposts_with_max_connections got "Truncate timed out"
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11157
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11157
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Stefania
>            Assignee: Stefania
>
> {{test_bulk_round_trip_blogposts_with_max_connections}} failed again but for a different
reason:
> http://cassci.datastax.com/view/Dev/view/krummas/job/krummas-marcuse-11148-trunk-dtest/1/testReport/junit/cqlsh_tests.cqlsh_copy_tests/CqlshCopyTest/test_bulk_round_trip_blogposts_with_max_connections/
> Increasing cqlsh {{--request-timeout}} should fix this since it is just the TRUNCATE
operation that times out, unlike the problems of CASSANDRA-10938.



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

Mime
View raw message