cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10524) Add ability to skip TIME_WAIT sockets on port check on Windows startup
Date Fri, 16 Oct 2015 14:54:05 GMT

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

Andy Tolbert commented on CASSANDRA-10524:
------------------------------------------

I have 12 nodes constantly rolling and things are running pretty reliable except I caught
another state {{SYN_SENT}} on 9042 shortly after shutdown, although it could be that I'm just
cycling the nodes too quickly as I wouldn't expect to see this state hang around.

> Add ability to skip TIME_WAIT sockets on port check on Windows startup
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-10524
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10524
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>            Priority: Trivial
>              Labels: Windows
>             Fix For: 3.0.0 rc2, 2.2.4
>
>         Attachments: win_aggressive_startup.txt
>
>
> C* sockets are often staying TIME_WAIT for up to 120 seconds (2x max segment lifetime)
for me in my dev environment on Windows. This is rather obnoxious since it means I can't launch
C* for up to 2 minutes after stopping it.
> Attaching a patch that adds a simple -a for aggressive startup to the launch scripts
to ignore duplicate port check from netstat if it's TIME_WAIT. Also snuck in some more liberal
interpretation of help strings in the .ps1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message