cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14464) stop-server.bat -p ../pid.txt -f command not working on windows 2016
Date Fri, 01 Jun 2018 10:37:00 GMT


Jason Brown commented on CASSANDRA-14464:

[~sphirke] I do not have access to a Windows machine. nor have I actually used one within
the last decade. The only other folks on the git blame for various Windows files are [~blerer]
or [~pauloricardomg].

> stop-server.bat -p ../pid.txt -f command not working on windows 2016
> --------------------------------------------------------------------
>                 Key: CASSANDRA-14464
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Shyam Phirke
>            Priority: Critical
> 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
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message