cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-256) Improve ListenAddress in Storage-Conf
Date Thu, 25 Jun 2009 15:58:07 GMT

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

Eric Evans commented on CASSANDRA-256:
--------------------------------------

0.0.0.0 is synonymous for "any", the expectation would be that cassandra will respond on "any"
of the node's addresses, (that it is bound to all of them). That is definitely not going to
work.

Leaving it blank essentially leaves it up to InetAddress.getLocalHost(). This will always
do the Right Thing *if* the node is properly configured (hostname, name resolution, etc),
and the Right Thing is to use the address associated with the hostname (it might not be).



> Improve ListenAddress in Storage-Conf
> -------------------------------------
>
>                 Key: CASSANDRA-256
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-256
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>
> Right now in storage-conf we have:
> <ListenAddress>localhost</ListenAddress>
> We should probably change this to 0.0.0.0 by default for new comers, since setting up
multi-node installation with localhost, isn't going to work right. Right now 0.0.0.0 might
not work right, (leaving blank does). So we should check that in DatabaseDescriptor. Also
a nice to have is maybe an XML doc comment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message