Re: Thrift message length exceeded

2013-04-24 Thread Lanny Ripple
le wrote: > >>> > >>>> We are using Astyanax in production but I cut back to just Hadoop and > >>>> Cassandra to confirm it's a Cassandra (or our use of Cassandra) problem. > >>>> > >>>> We do have some extre

Re: Thrift message length exceeded

2013-04-22 Thread Oleksandr Petrov
gt;>>> >> On 16/04/2013, at 10:17 AM, Lanny Ripple >>>> wrote: >>>> >> >>>> >>> A bump to say I found this >>>> >>> >>>> >>> >>>> http://stackoverflow.com/questions/15487540/pig-cassandra-message-

Re: Thrift message length exceeded

2013-04-21 Thread Oleksandr Petrov
anged since 1.1.5 when we didn't see such things but sure looks like >>> there's a bug that's slipped in (or been uncovered) somewhere. I'll try to >>> narrow down to a dataset and code that can reproduce. >>> >>> >>> >>> On

Re: Thrift message length exceeded

2013-04-20 Thread Oleksandr Petrov
ere's a bug that's slipped in (or been uncovered) somewhere. I'll try to >> narrow down to a dataset and code that can reproduce. >> >>> >> >>> On Apr 10, 2013, at 6:29 PM, Lanny Ripple >> wrote: >> >>> >> >>>> We ar

Re: Thrift message length exceeded

2013-04-20 Thread Oleksandr Petrov
; changed. Perhaps we were doing something wrong earlier that 1.2.3 exposed > but surprises are never welcome in production. > >>>> > >>>> On Apr 10, 2013, at 8:10 AM, wrote: > >>>> > >>>>> I also saw this when upgrading from C* 1.0 to 1.2.

Re: Thrift message length exceeded

2013-04-17 Thread Lanny Ripple
t;>> with 1.1.5 to almost everything carping with 1.2.3. Something has >>>> changed. Perhaps we were doing something wrong earlier that 1.2.3 exposed >>>> but surprises are never welcome in production. >>>> >>>> On Apr 10, 2013, at

Re: Thrift message length exceeded

2013-04-17 Thread aaron morton
t; to 0.8 >>>> Turns out the Thrift message really was too long. >>>> The mystery to me: Why no complaints in previous versions? Were some >>>> checks added in Thrift or Hector? >>>> >>>> -Original Message- >>>> Fr

Re: Thrift message length exceeded

2013-04-17 Thread Lanny Ripple
ded in Thrift or Hector? > > -Original Message- > From: Lanny Ripple [mailto:la...@spotright.com] > Sent: Tuesday, April 09, 2013 6:17 PM > To: user@cassandra.apache.org > Subject: Thrift message length exceeded > > Hello, > > We have recently upgraded to Cass 1.2.3 fro

Re: Thrift message length exceeded

2013-04-16 Thread aaron morton
out the Thrift message really was too long. >>> The mystery to me: Why no complaints in previous versions? Were some checks >>> added in Thrift or Hector? >>> >>> -Original Message- >>> From: Lanny Ripple [mailto:la...@spotright.com] >>&g

Re: Thrift message length exceeded

2013-04-15 Thread Lanny Ripple
complaints in previous versions? Were some checks >> added in Thrift or Hector? >> >> -Original Message- >> From: Lanny Ripple [mailto:la...@spotright.com] >> Sent: Tuesday, April 09, 2013 6:17 PM >> To: user@cassandra.apache.org >> Subj

Re: Thrift message length exceeded

2013-04-10 Thread Edward Capriolo
in previous versions? Were some > checks added in Thrift or Hector? > > > > -Original Message- > > From: Lanny Ripple [mailto:la...@spotright.com] > > Sent: Tuesday, April 09, 2013 6:17 PM > > To: user@cassandra.apache.org > > Subject: Thrift message

Re: Thrift message length exceeded

2013-04-10 Thread Lanny Ripple
oo long. > The mystery to me: Why no complaints in previous versions? Were some checks > added in Thrift or Hector? > > -Original Message- > From: Lanny Ripple [mailto:la...@spotright.com] > Sent: Tuesday, April 09, 2013 6:17 PM > To: user@cassandra.apache.org > S

RE: Thrift message length exceeded

2013-04-10 Thread moshe.kranc
...@spotright.com] Sent: Tuesday, April 09, 2013 6:17 PM To: user@cassandra.apache.org Subject: Thrift message length exceeded Hello, We have recently upgraded to Cass 1.2.3 from Cass 1.1.5. We ran sstableupgrades and got the ring on its feet and we are now seeing a new issue. When we run MapReduce

Thrift message length exceeded

2013-04-09 Thread Lanny Ripple
Hello, We have recently upgraded to Cass 1.2.3 from Cass 1.1.5. We ran sstableupgrades and got the ring on its feet and we are now seeing a new issue. When we run MapReduce jobs against practically any table we find the following errors: 2013-04-09 09:58:47,746 INFO org.apache.hadoop.util.Nat