[
https://issues.apache.org/jira/browse/CASSANDRA-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692981#comment-16692981
]
Dinesh Joshi commented on CASSANDRA-14829:
------------------------------------------
Hi [~georg], I am not a Windows user. If dtest cannot execute on Windows then
perhaps we can skip it. Getting dtest working on Windows is beyond the scope of
this ticket. I just wanted to ensure that we can avoid a regression in the
future. For now, I'll try to test this on my Windows VM and if it works, we can
find a committer to merge your change. Have you tried this fix on 3.x and trunk?
> Make stop-server.bat wait for Cassandra to terminate
> ----------------------------------------------------
>
> Key: CASSANDRA-14829
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14829
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Environment: Windows 10
> Reporter: Georg Dietrich
> Assignee: Georg Dietrich
> Priority: Minor
> Labels: easyfix, windows
> Fix For: 3.11.x, 4.x, 4.0.x
>
>
> While administering a single node Cassandra on Windows, I noticed that the
> stop-server.bat script returns before the cassandra process has actually
> terminated. For use cases like creating a script "shut down & create backup
> of data directory without having to worry about open files, then restart", it
> would be good to make stop-server.bat wait for Cassandra to terminate.
> All that is needed for that is to change in
> apache-cassandra-3.11.3\bin\stop-server.bat "start /B powershell /file ..."
> to "start /WAIT /B powershell /file ..." (additional /WAIT parameter).
> Does this sound reasonable?
> Here is the pull request: https://github.com/apache/cassandra/pull/287
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
