[
https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083430#comment-13083430
]
Jackson Chung commented on CASSANDRA-2967:
------------------------------------------
i wouldn't say it is lhf, this is quite important in terms of network security.
not adding value here, just a ref site similar to the above blog (its just from
official Sun's page).
http://download.oracle.com/javase/6/docs/technotes/guides/management/agent.html
see "Monitoring Applications through a Firewall" section if tl;dr
> 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
> Components: Tools
> Affects Versions: 0.8.2
> Reporter: Joaquin Casares
> Priority: Minor
> Labels: lhf
>
> 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
