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
Don't know if you tried this yet, but Eric noticed a bug in my patch.
There's a new one now, fixed.
-Jonathan
% ant release
Buildfile: build.xml
build-subprojects:
init:
[mkdir] Created dir:
/spool/home/teodor/cvs/Cassandra/cassandra-0.4/build/classes
[mkdir] Created dir:
/spool/home/teodor/cvs/Cassandra/cassandra-0.4/build/test/classes
[mkdir] Created dir:
fixed
2009/10/16 Teodor Sigaev teo...@sigaev.ru:
% ant release
Buildfile: build.xml
build-subprojects:
init:
[mkdir] Created dir:
/spool/home/teodor/cvs/Cassandra/cassandra-0.4/build/classes
[mkdir] Created dir:
/spool/home/teodor/cvs/Cassandra/cassandra-0.4/build/test/classes
Jonathan -
I patched in your latest change that dropped the assertions and tried
to restart my cluster on my old data. 2 of 5 nodes still failed to
start, with different errors.
One dies with a generic EOFException during recovery:
INFO - Compacting
Those are both consistent with a different bug that was fixed for
0.4.1 (now released officially!)
-Jonathan
On Fri, Oct 16, 2009 at 4:59 PM, Edmond Lau edm...@ooyala.com wrote:
Jonathan -
I patched in your latest change that dropped the assertions and tried
to restart my cluster on my old
