[
https://issues.apache.org/jira/browse/CASSANDRA-11073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139019#comment-15139019
]
Joshua McKenzie commented on CASSANDRA-11073:
---------------------------------------------
We've seen this at least a couple other times in dev environments. It'd be nice
if there's a way for us to check whether or not firewalls are running on
Windows and fire an alert if found (or if C* ports are blocked in built-in
firewall, for instance).
> Cannot contact other nodes on Windows 7 ccm
> -------------------------------------------
>
> Key: CASSANDRA-11073
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11073
> 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 {{127.0.0.1:random_port}} 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 127.0.0.2:50908 127.0.0.1:7000 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|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/net/OutboundTcpConnectionPool.java#L139]
> fixes the issue, but it's definitely not a solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
