cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3352) do not bind to a specific address for listening
Date Wed, 12 Oct 2011 19:25:11 GMT

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

Brandon Williams commented on CASSANDRA-3352:
---------------------------------------------

That's listen address.  Gossip and the storage protocol can only use one interface.
                
> do not bind to a specific address for listening
> -----------------------------------------------
>
>                 Key: CASSANDRA-3352
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3352
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Yang Yang
>            Priority: Minor
>
> now the thrift api binds to a specific address when it opens up the tcp socket.
> this creates a little inconvenience when you access the box in cassandra-cli:
> you have to find the exact host name. but if you are using cassandra-cli on localhost,
> you would normally like to just use "localhost"; similarly there is  a problem if
> you use EC2, you have to find the external address, instead of using the local ip, which
is available to you.
> I understand that the bind address would be useful in cases of testing (you can create
multiple
> clusters on the same box), but probably we could preserve that behavior through 
> a config var for testing mode only

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message