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/07/20 00:18:20 UTC
[jira] [Updated] (CASSANDRA-12235) dtest failure in
bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test
[ https://issues.apache.org/jira/browse/CASSANDRA-12235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Thompson updated CASSANDRA-12235:
----------------------------------------
Attachment: node4.log
node4_gc.log
node3.log
node3_gc.log
node3_debug.log
node2.log
node2_gc.log
node2_debug.log
node1.log
node1_gc.log
node1_debug.log
There isn't really much useful in the logs, other than the fact that node2 died about ten minutes before the test ended. Gc.log and debug.log don't really show a cause of death. I have to assume the oom killer?
> dtest failure in bootstrap_test.TestBootstrap.consistent_range_movement_true_with_ks_rf1_should_succeed_test
> ------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12235
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12235
> Project: Cassandra
> Issue Type: Test
> Reporter: Philip Thompson
> Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log, node4.log, node4_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.8_novnode_dtest/5/testReport/bootstrap_test/TestBootstrap/consistent_range_movement_true_with_ks_rf1_should_succeed_test
> Failed on CassCI build cassandra-3.8_novnode_dtest #5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)