I don't have an opinion on the default timeout. But in my experience
with other applications, you want to consciously make a choice about
what your timeout, based on your architecture and performance
requirements. You're much better off explicitly setting a timeout
that will cause your
Perhaps we should add this to the thrift/Cassandra FAQ?
On Oct 16, 2009, at 9:36 AM, Simon Smith simongsm...@gmail.com wrote:
I don't have an opinion on the default timeout. But in my experience
with other applications, you want to consciously make a choice about
what your timeout, based on
Simon,
I understand what you're saying and tend to agree with that philosophy.
I think the issue has more to do with the undocumentedness (if thats not a
word, it should be) of the Perl Thrift/Cassandra API in general. That is
something I hope to change in the near future. Timeouts are
What happens if you set it to 10?
On Oct 15, 2009, at 11:48 AM, Eric Lubow eric.lu...@gmail.com wrote:
My connection section of the script is here:
# Connect to the database
my $socket = new Thrift::Socket('localhost',9160);
$socket-setSendTimeout(2500);
I see a similar thing happening all the time. I get around it by closing
the current connection and reconnecting after a sleep. Although I am able
to do quite a few inserts between errors, so I'm not sure if it's the
exact problem.
-Anthony
On Thu, Oct 15, 2009 at 11:26:08AM -0400, Eric Lubow
Are you also using Perl?
On Thu, Oct 15, 2009 at 1:38 PM, Anthony Molinaro
antho...@alumni.caltech.edu wrote:
I see a similar thing happening all the time. I get around it by closing
the current connection and reconnecting after a sleep. Although I am able
to do quite a few inserts between
So I ran the tests again twice with a huge timeout and it managed to run in
just under 3 hours both times. So this issue is definitely related to the
timeouts. It might be worth changing the default timeouts for Perl to match
the infinite timeouts for Python. Thanks for the quick responses.
-e
