cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh McKenzie (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-16535) Fail to init Cassandra Startup with an API connected with other cluster machines (3.11.9 version)
Date Wed, 21 Jul 2021 16:01:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-16535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384968#comment-17384968
] 

Josh McKenzie commented on CASSANDRA-16535:
-------------------------------------------

Was thinking about opening a dev thread on removing windows support entirely, so unfortunately
not. That, and no windows env here.

[Performance under WSL 2 is close enough that windows is definitely a viable dev environment|https://www.phoronix.com/scan.php?page=article&item=wsl-wsl2-tr3970x&num=8]
option. I definitely recommend that route for correctness reasons.

> 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
>            Priority: Normal
>             Fix For: 3.11.11
>
>         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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message