Aramis created CASSANDRA-16535:
----------------------------------
Summary: Fail to init Cassandra Startup with an API connected with
other cluster machines (3.11.9 version)
Key: CASSANDRA-16535
URL: https://issues.apache.org/jira/browse/CASSANDRA-16535
Project: Cassandra
Issue Type: Bug
Components: Local/Startup and Shutdown
Reporter: Aramis
Assignee: Aramis
Attachments: cassandra_modified.ps1,
image-2021-03-24-21-12-32-709.png, image-2021-03-24-21-13-46-704.png
The code in the function "VerifyPortsAreAvailable", look for the ports: 7000,
9042, 7199 and 9160 in the "netstat -an" command output.
If we have an API connected to the cluster in a node, and we try to start the
execution of cassandra (with that API working, accesing ports 9042 of the other
cluster machines), the output of that command return us that the port is
already in use, and Cassandra´s startup process fails, showing the output
message : "port already in use" in the .log file.
Thus, if we change the code of the function, adding the line: " -and $line
-match "LISTENING" ", just next to the "$line -match "TCP" ", we will only
interrupt the execution if the load port is in the state: "LISTENING", but no
if it´s an active connection on the other node of the cluster.
!image-2021-03-24-21-12-32-709.png|width=470,height=159!
!image-2021-03-24-21-13-46-704.png|width=526,height=119!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
