[
https://issues.apache.org/jira/browse/CASSANDRA-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999180#comment-14999180
]
Paulo Motta commented on CASSANDRA-10646:
-----------------------------------------
This seems to be caused by two threads simultaneously accessing nodetool via
ccm (one to decomission a node, another to check the node status). The problem
is that ccm re-populates the cassandra-env file everytime nodetool is called,
so while one thread is opening the file, another thread tries to move the file,
what is not allowed on Windows.
Since it's not necessary to update the cassandra-env file everytime nodetool
(or any other tool) is called, I created a [CCM
PR|https://github.com/pcmanus/ccm/pull/406] that only updates the cassandra-env
file once per node lifetime, or when the install dir changes.
> crash_during_decommission_test dtest fails on windows
> -----------------------------------------------------
>
> Key: CASSANDRA-10646
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10646
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Paulo Motta
> Fix For: 3.1
>
>
> {{topology_test.py:TestTopology.crash_during_decommission_test}} flaps on on
> C* 3.0 on Windows:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/100/testReport/topology_test/TestTopology/crash_during_decommission_test/history/
> Since this test raises 2 errors on failure, there are 2 histories on CassCI
> for it:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/100/testReport/topology_test/TestTopology/crash_during_decommission_test_2/history/
> It looks like it fails because of contention over the temporary file where
> {{cassandra.env}} is stored:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/101/testReport/junit/topology_test/TestTopology/crash_during_decommission_test/
> Looks like this happens when {{nodetool status}} is called, since
> {{nodetool}} sources {{cassandra-env.sh}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
