[
https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152584#comment-13152584
]
Vijay commented on CASSANDRA-2967:
----------------------------------
Yes i have seen this happening in Java 6 not sure about java 7. Adding a agent
will not fix the System.gc issue, but it will just make it configurable to for
those it is ok (I mentioned the same in the Readme - github).
You can enable GC log and look for the Full GC's, DGC is the one which forces
every hour.
> 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
