You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yang Yang (Created) (JIRA)" <ji...@apache.org> on 2011/10/12 19:27:12 UTC
[jira] [Created] (CASSANDRA-3352) do not bind to a specific address
for listening
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
[jira] [Commented] (CASSANDRA-3352) do not bind to a specific
address for listening
Posted by "Brandon Williams (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CASSANDRA-3352) do not bind to a specific
address for listening
Posted by "Brandon Williams (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-3352.
-----------------------------------------
Resolution: Invalid
You can already specify 0.0.0.0 for rpc_address to bind all interfaces.
> 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
[jira] [Commented] (CASSANDRA-3352) do not bind to a specific
address for listening
Posted by "Yang Yang (Commented) (JIRA)" <ji...@apache.org>.
[ 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