[
https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278943#comment-13278943
]
Yuki Morishita commented on CASSANDRA-2967:
-------------------------------------------
In my opinion, I prefer to do this outside of Cassandra, since there already is
a way to achieve the goal using Vijay's javaagent when needed. Or when people
need security and binding to specific IP address, they can do those following
the blog post here
https://blogs.oracle.com/jmxetc/entry/jmx_connecting_through_firewalls_using.
> 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
> Reporter: Joaquin Casares
> Assignee: Alex Araujo
> Priority: Minor
> Labels: lhf
> Attachments: cassandra-0.8-2967.txt, cassandra-1.0-2967-v2.txt,
> cassandra-1.0-2967-v3.txt, cassandra-1.0-2967-v4.txt
>
>
> 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.
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
