[
https://issues.apache.org/jira/browse/CASSANDRA-11318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197612#comment-15197612
]
Philip Thompson commented on CASSANDRA-11318:
---------------------------------------------
Two minutes is already a pretty high timeout. I can see in the logs that the
node allegedly updated its understanding of the topology. It's unclear why
nodetool status isn't changing, though I can't compare timestamps of the status
calls with the logs. The logs also don't say *what* it is updating the topology
to.
I'm going to fix the annotation in dtest (It's on the wrong test), and maybe
wait if we see this again?
> dtest failure in
> replication_test.SnitchConfigurationUpdateTest.test_rf_collapse_property_file_snitch
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11318
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11318
> Project: Cassandra
> Issue Type: Test
> Reporter: Jim Witschey
> Assignee: Philip Thompson
> Labels: dtest
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/592/testReport/replication_test/SnitchConfigurationUpdateTest/test_rf_collapse_property_file_snitch
> Failed on CassCI build cassandra-3.0_dtest #592
> The test failed on this line:
> https://github.com/riptano/cassandra-dtest/blob/7a331cda807c96ae107b58017854f0e57996d8c3/replication_test.py#L567
> So, a node's expected move from one rack to another doesn't happen in the
> allotted timeout time. This is the only flap I've seen. Maybe the thing to do
> here is increase the timeout and keep an eye on it?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
