Shyam Phirke created CASSANDRA-14464:
----------------------------------------
Summary: stop-server.bat -p ../pid.txt -f command not working on
windows 2016
Key: CASSANDRA-14464
URL: https://issues.apache.org/jira/browse/CASSANDRA-14464
Project: Cassandra
Issue Type: Bug
Reporter: Shyam Phirke
Steps to reproduce:
1. Copy and extract cassandra binaries on windows 2016 machine
2. Start cassandra in non-legacy mode
3. Check pid of cassandra in task manager and compare it with in pid.txt
4. Now stop cassandra using command stop-server.bat -p ../pid.txt -f
Expected:
After executing <cassandra_installed_location>\bin:\> stop-server.bat -p
../pid.txt -f
cassandra process as in pid.txt should get killed.
Actual:
After executing above stop command, the cassandra process as in pid.txt gets
killed but a new process gets created with new pid. Also the pid.txt not
updated with new pid.
This new process should not get created.
Please comment on this issue if more details required.
I am using cassandra 3.11.2.
This issue impacting me much since because of this new process getting created
my application uninstallation getting impacted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
