node tool passes the host name un modified to the JMX library to connect to the
host.
The JMX server will, by default, bind to the ip address of the machine.
If the host name was wrong, I would guess the JMX service failed to bind.
Cheers
-
Aaron Morton
Freelance Developer
@
-
From: Douglas Muth
Sent: Tuesday, May 29, 2012 11:39 AM
To: user@cassandra.apache.org
Subject: Re: Nodetool talking to an old IP address (and timing out)
8 hours, 1 cup of coffee, and 4 Advil later, and I think I got the
bottom of this. Not having much of a Java or JMX background, I'll t
8 hours, 1 cup of coffee, and 4 Advil later, and I think I got the
bottom of this. Not having much of a Java or JMX background, I'll try
to explain it the best that I can.
To recap, my machine originally had the IP address of 10.244.207.16.
Then I shutdown/restarted that EC2 instance, and it had
I'm afraid that did not work. I'm running JMX on port 7199 (the
default) and I verified that the port is open and accepting
connections.
Here's what I'm seeing:
dmuth@devteam:~/cliq (production) $ nodetool --host localhost --port 7199 ring
Error connection to remote JMX agent!
java.rmi.ConnectEx
specify the jmx port to nodetool, hard coded in conf/cassandra-env.sh
nodetool -h localhost -p [jmx port] ring
2012/5/27 Douglas Muth
> Hi folks,
>
> I'm a relative newbie to Cassandra, and have been trying to get up to
> speed on it so that I can start using it at $WORK.
>
> I ran into an inte
Hi folks,
I'm a relative newbie to Cassandra, and have been trying to get up to
speed on it so that I can start using it at $WORK.
I ran into an interesting issue the other day with nodetool. I
currently have Cassandra running on an Amazon EC2 instance running
Ubuntu 10.10. At one point, I rebo
