[
https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072507#comment-13072507
]
Nick Bailey commented on CASSANDRA-2967:
----------------------------------------
I'm pretty sure that setting doesn't control the interface jmx binds to, only
the interface jmx tells a client to connect to when it does it's crazy
2-connection communication dance.
I'd say this is still a valid ticket. Seems to be an example of how to do it
here:
http://vafer.org/blog/20061010091658/
> Only bind JMX to the same IP address that is being used in Cassandra
> --------------------------------------------------------------------
>
> Key: CASSANDRA-2967
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2967
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Joaquin Casares
> Priority: Minor
>
> The setup is 5 nodes in each data center are all running on one physical test
> machine and even though the repair was run against the correct IP the wrong
> JMX port was used. As a result, instead of repairing all 5 nodes I was
> repairing the same node 5 times.
> It would be nice if Cassandra's JMX would bind to only the IP address on
> which its thrift/RPC services are listening on instead of binding to all IP's
> on the box.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
