You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jacques-Henri Berthemet (JIRA)" <ji...@apache.org> on 2017/03/28 14:19:41 UTC

[jira] [Created] (CASSANDRA-13386) Can't start Cassandra with powershell script when connections are already established to other Cassandra nodes on the same host

Jacques-Henri Berthemet created CASSANDRA-13386:
---------------------------------------------------

             Summary: Can't start Cassandra with powershell script when connections are already established to other Cassandra nodes on the same host
                 Key: CASSANDRA-13386
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13386
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Windows with powershell
            Reporter: Jacques-Henri Berthemet


In our test env we run our client application on the same host as Cassandra nodes. When we restart the Cassandra node when the application is still running it fails in VerifyPortsAreAvailable function of bin\cassandra.ps1:98 with the below error:

{code}
VerifyPortsAreAvailable : Found a port already in use. Aborting startup
At C:\apache-cassandra-2.2.7\bin\cassandra.ps1:98 char:9
+         VerifyPortsAreAvailable
+         ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,VerifyPortsAreAvailable

VerifyPortsAreAvailable :   TCP    xxx.xx.xx.171:61936    xxx.xx.xx.24:9042      ESTABLISHED
{code}

It looks like VerifyPortsAreAvailable is picking a remote 9042 port and refuses to start Cassandra.

The VerifyPortsAreAvailable function should be fixed so that it only looks for LISTENING ports.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)