[
https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151852#comment-13151852
]
Vijay commented on CASSANDRA-2967:
----------------------------------
Plz note:
http://download.oracle.com/javase/6/docs/technotes/guides/management/agent.html
enables the RMI server, which will in-turn do System.gc every 60 min. I have
tried it before and reverted because of the same.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6200091 you might want to
use DisableExplicitGC gc option or you might want to increase the
-Dsun.rmi.dgc.server.gcInterval=600000 both of which might be kind of dangerous
depnds on how people use it.
> 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
> 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
