cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-11073) Cannot contact other nodes on Windows 7 ccm
Date Mon, 01 Feb 2016 14:37:39 GMT


Paulo Motta resolved CASSANDRA-11073.
    Resolution: Not A Problem

> Cannot contact other nodes on Windows 7 ccm
> -------------------------------------------
>                 Key: CASSANDRA-11073
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>         Environment: windows 7
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: windows
> Before CASSANDRA-9309 was fixed the {{OutboundTcpConnectionPool}} did not bind the client
socket to a specific ip/port, so the Windows kernel always picked {{}}
as client socket address for ccm nodes, regardless of the {{listen_address}} value.
> After fixing CASSANDRA-9309 the {{OutboundTcpConnectionPool}} now binds outgoing client
sockets to {{listen_address:random_port}}.
> So any ccm cluster with more than one node will bind client sockets to {{127.0.0.n}}
where n is the node id.
> However, the nodes cannot contact each other because connections remain in the {{SYN_SENT}}
state on Windows 7, as shown by netstats:
> {noformat}
>   TCP         SYN_SENT
> {noformat}
> This bug is preventing the execution of dtests on Windows 7, and was also experienced
by [~Stefania].
> I suspect its a configuration/environment problem, but firewall and group policies are
disabled. The funny thing is that it does not happen on cassci, but afaik there are no Windows
7 nodes there
> Commenting [this line|]
fixes the issue, but it's definitely not a solution.

This message was sent by Atlassian JIRA

View raw message