cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arya Goudarzi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1412) Internal error processing batch_mutate
Date Mon, 13 Sep 2010 23:53:33 GMT

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

Arya Goudarzi commented on CASSANDRA-1412:
------------------------------------------

OK. This is still reproducible. It seams that it has something to do with numerical row keys,
here are steps for reproduction:

1. Setup a 3 node cluster;
2. Load Keyspace1 with RF=3;
3. Try to insert a row with a numerical key like "1234" into StandardByUUID1 ColumnFamily

You will get the above mentioned Assertion Error. You can reproduce this even with CLI or
testing it with cluster_tool get_endpoints. Here is an example that does no work:

[agoudarzi@cas-test1 ~]$ clustertool --host=10.50.26.132 get_endpoints agoudarzi_Keyspace1
cf_1
Exception in thread "main" java.lang.AssertionError
	at org.apache.cassandra.locator.AbstractReplicationStrategy.getNaturalEndpoints(AbstractReplicationStrategy.java:91)
	at org.apache.cassandra.service.StorageService.getNaturalEndpoints(StorageService.java:1338)
	at org.apache.cassandra.service.StorageService.getNaturalEndpoints(StorageService.java:1326)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111)
	at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45)
	at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:226)
	at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
	at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:251)
	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:857)
	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:795)
	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1449)
	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:90)
	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1284)
	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1382)
	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:807)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
	at sun.rmi.transport.Transport$1.run(Transport.java:177)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)

And here is an example that works:

[agoudarzi@cas-test1 ~]$ clustertool --host=10.50.26.132 get_endpoints agoudarzi_Keyspace1
"cf_\2"
Key              : cf_\2
Endpoints        : [/10.50.26.132, /10.50.26.133, /10.50.26.134]

Now, why escaping fixed this? You can also try a full numeric key and it fails.




> Internal error processing batch_mutate
> --------------------------------------
>
>                 Key: CASSANDRA-1412
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1412
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>         Environment: CentOS 5.2
> svn co -r 987305, August 19th
>            Reporter: Arya Goudarzi
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: node1.log, node2.log, node3.log
>
>
> I have a 3 node cluster with existing data on it which where inserted using the version
on trunc on August 15th. Today, I was trying to insert a row with a single column and value
larger than 8k and I got Internal Error which in the logs is as follows:
> ERROR [pool-1-thread-21] 2010-08-19 17:10:35,122 Cassandra.java (line 2988) Internal
error processing batch_mutate
> java.lang.AssertionError
> 	at org.apache.cassandra.locator.AbstractReplicationStrategy.getNaturalEndpoints(AbstractReplicationStrategy.java:91)
> 	at org.apache.cassandra.service.StorageService.getNaturalEndpoints(StorageService.java:1289)
> 	at org.apache.cassandra.service.StorageService.getNaturalEndpoints(StorageService.java:1277)
> 	at org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:106)
> 	at org.apache.cassandra.thrift.CassandraServer.doInsert(CassandraServer.java:468)
> 	at org.apache.cassandra.thrift.CassandraServer.batch_mutate(CassandraServer.java:438)
> 	at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.process(Cassandra.java:2980)
> 	at org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:2499)
> 	at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:167)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:636)
> I got the same exception before on the version which I was running in CASSANDRA-1384
and I also mentioned it there, but I think this is a different one and has nothing to do with
Migration Stage, so filing a separate issue.
> Please investigate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message