Sure is: scale7-pelops-1.1-0.7.x-20110418.225848-3.jar
Cheers,
--
Dan Washusen
On Tuesday, 19 April 2011 at 3:58 PM, Héctor Izquierdo Seliva wrote:
> Thanks Dan for fixing that! Is the change integrated in the latest maven
> snapshot?
>
> El mar, 19-04-2011 a las 10:48 +1000, Dan Washusen escri
Thanks Dan for fixing that! Is the change integrated in the latest maven
snapshot?
El mar, 19-04-2011 a las 10:48 +1000, Dan Washusen escribió:
> An example scenario (that is now fixed in Pelops):
> 1. Attempt to write a column with a null value
> 2. Cassandra throws a TProtocolException
An example scenario (that is now fixed in Pelops):
Attempt to write a column with a null value
Cassandra throws a TProtocolException which renders the connection useless for
future operations
Pelops returns the corrupt connection to the pool
A second read operation is attempted with the corrupt co
Any idea what's causing the original TPE?
On Mon, Apr 18, 2011 at 6:22 PM, Dan Washusen wrote:
> It turns out that once a TProtocolException is thrown from Cassandra the
> connection is useless for future operations. Pelops was closing connections
> when it detected TimedOutException, TTransportE
It turns out that once a TProtocolException is thrown from Cassandra the
connection is useless for future operations. Pelops was closing connections
when it detected TimedOutException, TTransportException and
UnavailableException but not TProtocolException. We have now changed Pelops to
close c
I've looked over the Pelops code again and I really can't see how it could be
at fault here...
--
Dan Washusen
On Wednesday, 13 April 2011 at 3:20 AM, Stephen McKamey wrote:
> [I wrote this Apr 10, 2011 at 12:09 but my message seems to have gotten lost
> along the way.]
>
> I use Pelops (the
Pelops uses a single connection per operation from a pool that is backed by
Apache Commons Pool (assuming you're using Cassandra 0.7). I'm not saying it's
perfect but it's NOT sharing a connection over multiple threads.
Dan Hendry mentioned that he sees these errors. Is he also using Pelops? Fro
El mié, 06-04-2011 a las 21:04 -0500, Jonathan Ellis escribió:
> "out of sequence response" is thrift's way of saying "I got a response
> for request Y when I expected request X."
>
> my money is on using a single connection from multiple threads. don't do
> that.
>
I'm not using thrift direct
El mié, 06-04-2011 a las 21:04 -0500, Jonathan Ellis escribió:
> "out of sequence response" is thrift's way of saying "I got a response
> for request Y when I expected request X."
>
> my money is on using a single connection from multiple threads. don't do
> that.
I'm not using thrift direc
"out of sequence response" is thrift's way of saying "I got a response
for request Y when I expected request X."
my money is on using a single connection from multiple threads. don't do that.
On Wed, Apr 6, 2011 at 5:59 PM, Dan Washusen wrote:
> Pelops will retry when TimedOutException, TTransp
Pelops will retry when TimedOutException, TTransportException or
UnavailableException exceptions are thrown but not TApplicationException.
TApplicationException has a type property which looks like it could be used to
retry based on specific values. Based on the names the INTERNAL_ERROR and
BAD
El mié, 06-04-2011 a las 09:06 +1000, Dan Washusen escribió:
> Pelops raises a RuntimeException? Can you provide more info please?
>
org.scale7.cassandra.pelops.exceptions.ApplicationException:
batch_mutate failed: out of sequence response
> --
> Dan Washusen
> Make big files fly
> visit digit
Pelops raises a RuntimeException? Can you provide more info please?
--
Dan Washusen
Make big files fly
visit digitalpigeon.com
On Tuesday, 5 April 2011 at 11:43 PM, Héctor Izquierdo Seliva wrote:
El mar, 05-04-2011 a las 09:35 -0400, Dan Hendry escribió:
> > I too have seen the out of sequence r
13 matches
Mail list logo
