Nodetool gives cryptic errors when given a nonexistent keyspace arg
-------------------------------------------------------------------
Key: CASSANDRA-1143
URL: https://issues.apache.org/jira/browse/CASSANDRA-1143
Project: Cassandra
Issue Type: Improvement
Components: Tools
Affects Versions: 0.6.1
Environment: Sun Java 1.6u20, Cassandra 0.6.2, CentOS 5.5.
Reporter: Ian Soboroff
Priority: Minor
I typoed the keyspace arg to 'nodetool repair', and got the following exception:
/usr/local/src/cassandra/bin/nodetool --host node4 repair DocDb
Exception in thread "main" java.lang.RuntimeException: No replica strategy
configured for DocDb
at
org.apache.cassandra.service.StorageService.getReplicationStrategy(StorageService.java:246)
at
org.apache.cassandra.service.StorageService.constructRangeToEndPointMap(StorageService.java:466)
at
org.apache.cassandra.service.StorageService.getRangeToAddressMap(StorageService.java:452)
at
org.apache.cassandra.service.AntiEntropyService.getNeighbors(AntiEntropyService.java:145)
at
org.apache.cassandra.service.StorageService.forceTableRepair(StorageService.java:1075)
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:619)
It would be better to report that the keyspace doesn't exist, rather than the
keyspace doesn't have a replication strategy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
