Aaron,
It seems that we had a beta-1 node in our cluster of beta-2'. Haven't had
the problem since.
Thanks for the help,
Frank
On Sat, Oct 16, 2010 at 1:50 PM, aaron morton wrote:
> Frank,
>
> Things are a bit clearer now. Think I had the wrong idea to start with.
>
> The server side error me
Frank,
Things are a bit clearer now. Think I had the wrong idea to start with.
The server side error means this cassandra node does not know about the
column family it was asked to read. I guess either the schema are out of sync
on the nodes or there is a bug. How did you add
Aaron,
I updated the cassandra files and but still receive the same error (on
client side) with a different line number 551:
org.apache.thrift.TApplicationException: Internal error processing get_slice
at
org.apache.thrift.TApplicationException.read(TApplicationException.java:108)
at
org.apache.c
Am guessing but it looks like cassandra returned an error and the client then had trouble reading the error. However if I look at the Beta 2 java thrift interface in Cassandra.java, line 544 is not in recv_get_slice. May be nothing. Perhaps check the server for an error and double check your client
10:10:21,787 ERROR ~ Error getting Sensor
org.apache.thrift.TApplicationException: Internal error processing get_slice
at org.apache.thrift.TApplicationException.read(
TApplicationException.java:108)
at org.apache.cassandra.thrift.Cassandra$Client.recv_get_slice(
Cassandra.java:544)
at org.apac
10:10:21,787 ERROR ~ Error getting Sensor
org.apache.thrift.TApplicationException: Internal error processing get_slice
at org.apache.thrift.TApplicationException.read(
TApplicationException.java:108)
at org.apache.cassandra.thrift.Cassandra$Client.recv_get_slice(
Cassandra.java:544)
at org.apac
