cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10644) multiple repair dtest fails under Windows
Date Mon, 16 Nov 2015 17:17:11 GMT

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

Aleksey Yeschenko updated CASSANDRA-10644:
------------------------------------------
    Fix Version/s: 3.0.1

> multiple repair dtest fails under Windows
> -----------------------------------------
>
>                 Key: CASSANDRA-10644
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10644
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jim Witschey
>            Assignee: Paulo Motta
>             Fix For: 2.2.4, 3.0.1, 3.1
>
>
> {{incremental_repair_test.py:TestIncRepair.multiple_repair_test}} flaps on CassCI Windows
runs on C* 3.0:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/100/testReport/junit/incremental_repair_test/TestIncRepair/multiple_repair_test/history/
> The error is {{An existing connection was forcibly closed by the remote host}}, and happens
consistently in the failing runs:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/100/testReport/junit/incremental_repair_test/TestIncRepair/multiple_repair_test/
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/72/testReport/junit/incremental_repair_test/TestIncRepair/multiple_repair_test/
> [~yukim] Can you have a look? I feel like you're more likely than anyone else to understand
the streaming error. In particular: is this what happens when a node goes down? This could
be an environment error, rather than a C* bug.



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

Mime
View raw message