Hello,
Thanks for the help. There was a problem in the code actually... The
connection object was not thread safe. That is why the messages were so
big.
After fixing that we do not get any errors. The cluster seems stable.
Thanks again for all the help.
Regards,
Vasilis
On Thu, Jul 5, 2012
agree.
It's a good idea to remove as many variables and possible and get to a
stable/known state. Use a clean install and a well known client and see if the
problems persist.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 5/07/2012, a
On Jul 4, 2012 2:02 PM, "Vasileios Vlachos"
wrote:
>
> Any ideas what could be causing strange message lengths?
One cause of this that I've seen is a client using unframed Thrift
transport while the server expects framed, or vice versa. I suppose a
similar cause could be something that is not a T
We also get negative message lengths occasionally... Please see below:
ERROR 12:49:00,777 Thrift error occurred during processing of message.
org.apache.thrift.TException: Negative length: -2147483634
at
org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(TBinaryProtocol.java:388)
Hello Aaron, thanks for your email.
- That's pretty small, try m1.xlarge.
Yes, this is small. We are aware of that, but that doesn't seem to be the
actual problem. But we cannot see any reason why this shouldn't work as a
test environment. After we get a fair understanding we are going to invest
> We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core),
That's pretty small, try m1.xlarge.
> e are still not sure what version of thrift to use with Cassandra 1.0.7 (we
> are still getting the same message regarding the 'old client').
1.0.7 ships with thrift 0.6
What clie
Just an update to correct something...
The application hits 10.128.16.111. The last lines of Error #4 suggest
that 10.128.16.110 and 10.128.16.112 where down because Cassandra service
was down on 10.128.16.111 and it could not detect the cluster (I think it
must be gossip related, right???).
Than
Hello All,
We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core),
running Ubuntu 12.04. We have three nodes in the cluster and we hit only
one node from our application. Thrift version is 0.6.1 (we changed from 0.8
because we thought there was a compatibility problem between th
