cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2967) Only bind JMX to the same IP address that is being used in Cassandra
Date Tue, 29 Nov 2011 10:19:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159183#comment-13159183
] 

Yuki Morishita commented on CASSANDRA-2967:
-------------------------------------------

Patch works fine for basic use case(binding agent to specified address), but we we cannot
use SSL or password based auth any more, which out-of-the-box JMX agent supports via system
properties.
AFAIK you have to implement those to JmxRemoteListener like the one described below.

http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html#gdfvv

I don't know how many people need those functionalities(SSL/auth), but since default JMX agent
supports those, we also should add those functionalities.

I think it would be better to provide javaagent version of module like Vijay implemented with
SSL/Auth support. Or maybe just give pointer to his module in somewhere?
                
> 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

        

Mime
View raw message