to be monitoring the frequency of
timeouts, so if they increase over the baseline you can track down the
cause and fix it.
Just my $0.02.
Simon
On Thu, Oct 15, 2009 at 11:33 PM, Eric Lubow eric.lu...@gmail.com wrote:
So I ran the tests again twice with a huge timeout and it managed to run
in
just
Using the Thrift Perl API into Cassandra, I am running into what is
endearingly referred to as the 4 bytes of doom:
TSocket: timed out reading 4 bytes from localhost:9160
The script I am using is fairly simple. I have a text file that has about
3.6 million lines that are formatted like:
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
