cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3348) NPE when running nodetool info on secondary interface
Date Tue, 11 Oct 2011 22:11:11 GMT

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

Brandon Williams commented on CASSANDRA-3348:
---------------------------------------------

Sounds like CASSANDRA-3186, the interface difference was likely just timing.
                
> NPE when running nodetool info on secondary interface
> -----------------------------------------------------
>
>                 Key: CASSANDRA-3348
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3348
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.7
>         Environment: ubuntu & cassandra 0.8.7 with two networks.  normal ec2 network
and vpn network
> listen_address: 172.1.1.136 (vpn network)
> rpc_address: 0.0.0.0
>            Reporter: Sasha Dolgy
>            Priority: Minor
>
> When nodetool is run against eth0:
> cassandra@ip-10-1-1-136:~$ nodetool -h 10.1.1.136 -p 9090 info
> Token            : 113427455640312821154458202477256070484
> Gossip active    : true
> Load             : 3.54 MB
> Generation No    : 1318365429
> Uptime (seconds) : 1052
> Heap Memory (MB) : 20.54 / 848.00
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.cassandra.locator.Ec2Snitch.getDatacenter(Ec2Snitch.java:93)
> 	at org.apache.cassandra.locator.DynamicEndpointSnitch.getDatacenter(DynamicEndpointSnitch.java:122)
> 	at org.apache.cassandra.locator.EndpointSnitchInfo.getDatacenter(EndpointSnitchInfo.java:49)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
> 	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
> 	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
> 	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
> 	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
> 	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
> 	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
> 	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
> 	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
> 	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
> 	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360)
> 	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:159)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> When nodetool is run against tun0:
> cassandra@ip-10-1-1-136:~$ nodetool -h 172.1.1.136 -p 9090 info
> Token            : 113427455640312821154458202477256070484
> Gossip active    : true
> Load             : 3.54 MB
> Generation No    : 1318365429
> Uptime (seconds) : 1250
> Heap Memory (MB) : 28.25 / 848.00
> Data Center      : ap-southeast
> Rack             : 1b
> Exceptions       : 0
> When I run 'nodetool ring' against either IP address, no NPE.  

--
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