cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2967) Only bind JMX to the same IP address that is being used in Cassandra
Date Fri, 18 Nov 2011 01:29:55 GMT


Alex Araujo commented on CASSANDRA-2967:

Are you sure that it's {{System.gc}}?  I thought RMI had a reference counting based "Distributed
Garbage Collector" that invokes a {{clean}} method just for remote objects.

Also, AFAIK, starting a {{JMXConnectorServer}} from a dynamically loaded javaagent is the
same as starting one from compiled code in an application (i.e., the same DGC behavior applies
to the JVM running the server regardless of how it's started).  If you don't notice a GC impact
when running your JmxProxy, chances are the built-in {{JMXConnectorServer}} code will not
have a noticeable impact as well.

Nevertheless, I think this warrants additional testing to verify my assumptions.  I'll post
my results when I get a chance to test this.
> Only bind JMX to the same IP address that is being used in Cassandra
> --------------------------------------------------------------------
>                 Key: CASSANDRA-2967
>                 URL:
>             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,
> 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:!default.jspa
For more information on JIRA, see:


View raw message