cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9280) Streaming connections should bind to the broadcast_address of the node
Date Fri, 01 May 2015 20:12:06 GMT

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

Jonathan Ellis commented on CASSANDRA-9280:
-------------------------------------------

2.0.x?

> Streaming connections should bind to the broadcast_address of the node
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-9280
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9280
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Richard Low
>            Assignee: Yuki Morishita
>            Priority: Minor
>
> Currently, if you have multiple interfaces on a server, a node receiving a stream may
show the stream as coming from the wrong IP in e.g. nodetool netstats. The IP is taken as
the source of the socket, which may not be the same as the node’s broadcast_address. The
outgoing socket should be explicitly bound to the broadcast_address.
> It seems like this was fixed a long time ago in CASSANDRA-737 but has since broken.



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

Mime
View raw message