cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11290) dtest failure in materialized_views_test.TestMaterializedViewsConsistency.single_partition_consistent_reads_after_write_test
Date Tue, 22 Mar 2016 18:27:25 GMT

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

Carl Yeksigian commented on CASSANDRA-11290:
--------------------------------------------

This looks like a real bug, but I'm not sure what is causing this. We don't allow a null lock
in the {{locks}} array, instead following a path that includes rescheduling, so it doesn't
seem like we should get to the end and have a null. The only other thing would be if the {{columnFamilyIds}}
changed during execution, so that {{size()}} was different, but other threads don't have access
to it, and we should also get a {{ConcurrentModificationException}}.

> 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: Bug
>            Reporter: Russ Hatch
>            Assignee: Carl Yeksigian
>              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)

Mime
View raw message