Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 12 Oct 2011 18:45:11 +0000 (UTC)
From: "Yang Yang (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <796171771.6025.1318445111995.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1585278394.5711.1318440432006.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3352) do not bind to a specific
 address for listening
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yang Yang commented on CASSANDRA-3352:
--------------------------------------

thanks

but could you please explain why this line is in the cassandra.yaml comment?

# Setting this to 0.0.0.0 is always wrong.

                
> 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