That means something sent a nonsense request to Cassandra. Often this
happens when a non-Cassandra client connects on the Thrift port.
On Thu, Jul 14, 2011 at 3:01 AM, Donna Li wrote:
> All:
>
> What is the following error mean?
>
>
>
> ERROR [pool-1-thread-62] 2011-07-14 14:31:04,671
>
All:
What is the following error mean?
ERROR [pool-1-thread-62] 2011-07-14 14:31:04,671
CustomTThreadPoolServer.java (line 173) Error occurred during processing
of message.
java.lang.NegativeArraySizeException
at
org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBina
Remove the cache file.
On Tue, Mar 29, 2011 at 11:44 AM, Wenjun Che wrote:
>
> even after I ran compact on all keyspaces. Cassandra exits after the
> exception so I can't try "nodetool scrub".
> There is just one node.
>
> java.lang.NegativeArraySizeException
> at
> org.apache.cassandra.db.C
even after I ran compact on all keyspaces. Cassandra exits after the
exception so I can't try "nodetool scrub".
There is just one node.
java.lang.NegativeArraySizeException
at
org.apache.cassandra.db.ColumnFamilyStore.readSavedCache(ColumnFamilyStore.java:280)
at
org.apache.cassandra.db.C
On Wed, Feb 16, 2011 at 10:01 PM, Nate McCall wrote:
> See the following mail thread:
> http://www.mail-archive.com/user@cassandra.apache.org/msg10183.html
>
> In short, running nodetool compact should clear it up.
>
>
Thanks for the pointer! I ran nodetool compact on my nodes, and so far it's
l
ed app (using python/pycassa/thrift) I'm getting the following
> NegativeArraySizeException. The traceback is below:
>
> ERROR 21:08:33,187 Fatal exception in thread Thread[ReadStage:219,5,main]
> java.lang.RuntimeException: java.lang.NegativeArraySiz
I recently upgraded to 0.7.2 from 0.7.0, and now when I run my
multi-threaded app (using python/pycassa/thrift) I'm getting the following
NegativeArraySizeException. The traceback is below:
ERROR 21:08:33,187 Fatal exception in thread Thread[ReadStage:219,5,main]
java.lang.RuntimeExce
