I should probably add.. /etc/hosts had the hostname set to 127.0.1.1.
On Thu, Sep 3, 2015 at 11:00 PM, Jason Lewis wrote:
> I figured this one out. As it turns out, the nodes that I couldn't
> connect to, had the hostname set to 127.0.1.1. The listen IP is *not*
> that IP.
>
> Thanks for the lo
I figured this one out. As it turns out, the nodes that I couldn't
connect to, had the hostname set to 127.0.1.1. The listen IP is *not*
that IP.
Thanks for the logging tip, it helped track it down.
On Thu, Sep 3, 2015 at 10:43 PM, Jason Lewis wrote:
> After enabling that option, I'm seeing er
After enabling that option, I'm seeing errors like this on the node I
can't connect to.
Sep 04, 2015 2:35:48 AM sun.rmi.server.UnicastServerRef logCallException
FINE: RMI TCP Connection(4)-127.0.0.1: [127.0.0.1] exception:
javax.management.InstanceNotFoundException:
org.apache.cassandra.metrics:t
> LOCAL_JMX=no
>
> if [ "$LOCAL_JMX" = "yes" ]; then
> JVM_OPTS="$JVM_OPTS -Dcassandra.jmx.local.port=$JMX_PORT
> -XX:+DisableExplicitGC"
> else
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.port=$JMX_PORT"
> JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT"
> JV
All of my nodes have the same cassandra-env.sh. Only a few of them complain.
LOCAL_JMX=no
if [ "$LOCAL_JMX" = "yes" ]; then
JVM_OPTS="$JVM_OPTS -Dcassandra.jmx.local.port=$JMX_PORT
-XX:+DisableExplicitGC"
else
JVM_OPTS="$JVM_OPTS -Dcom.sun.management.jmxremote.port=$JMX_PORT"
JVM_OPTS="$JV
On 08/25/2015 02:19 PM, Jason Lewis wrote:
I'm trying to run nodetool from one node, connecting to another. I
can successfully connect to the majority of nodes in my ring, but two
nodes throw the following error.
nodetool: Failed to connect to ':7199' NoSuchObjectException: 'no
such object in t
