You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2016/03/16 17:57:33 UTC
[jira] [Commented] (CASSANDRA-11290) dtest failure in
materialized_views_test.TestMaterializedViewsConsistency.single_partition_consistent_reads_after_write_test
[ https://issues.apache.org/jira/browse/CASSANDRA-11290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197670#comment-15197670 ]
Philip Thompson commented on CASSANDRA-11290:
---------------------------------------------
Based on {{DEBUG [GossipStage:1] 2016-02-11 19:15:10,989 FailureDetector.java:456 - Ignoring interval time of 2000760096 for /127.0.0.2}} in node3's log, it seems like just a shakey network problem to/from node2. We could add retry code to this method in dtest?
> dtest failure in materialized_views_test.TestMaterializedViewsConsistency.single_partition_consistent_reads_after_write_test
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11290
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11290
> Project: Cassandra
> Issue Type: Test
> Reporter: Russ Hatch
> Assignee: Philip Thompson
> Labels: dtest
> Fix For: 3.x
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_offheap_dtest/26/testReport/materialized_views_test/TestMaterializedViewsConsistency/single_partition_consistent_reads_after_write_test
> Failed on CassCI build trunk_offheap_dtest #26
> Failing infrequently but same error on at least two of those infrequent flaps:
> {noformat}
> Connection to 127.0.0.2 was closed
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)