[
https://issues.apache.org/jira/browse/CASSANDRA-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393301#comment-15393301
]
Joel Knighton commented on CASSANDRA-12260:
-------------------------------------------
That definitely seems to be the problem. The node should eventually shut down -
after that message is printed, it just needs to execute the StorageService
shutdown hook (and the JVM to exit). How long we should need to wait for that
is a good question - evidently, it can be quite slow on CI. That said, it takes
about two tenths of a second on my machine. If we're passing the thirty seconds
here with no other symptoms (and that's what I see so far), there is something
going pretty poorly in either C* or the test environment, and it might be
better to investigate rather than change the test.
To be more helpful in debugging this, I'd need trace level logging.
Unfortunately, due to [CASSANDRA-12011], we lose logging in the shutdown hook,
so we'd need a hacky fix to do that. I can do some or all of 1) a hacky branch
fixing [CASSANDRA-12011], 2) running with trace logging on CI to try to repro,
3) analyzing those results.
> dtest failure in
> topology_test.TestTopology.decommissioned_node_cant_rejoin_test
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-12260
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12260
> Project: Cassandra
> Issue Type: Test
> Reporter: Philip Thompson
> Assignee: Philip Thompson
> 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
>
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.9_novnode_dtest/14/testReport/topology_test/TestTopology/decommissioned_node_cant_rejoin_test
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
