e took down the Cassandra node with the faulty
>> commit log disk, the client continued to write and didn't seem to bother
>> (which is what we expected to happen in the first place, but didn't).
>>
>> From: aaron morton [mailto:aa...@thelastpickle.com]
>> Sent: Monday
And to add to that – when we took down the Cassandra node with the faulty
> commit log disk, the client continued to write and didn't seem to bother
> (which is what we expected to happen in the first place, but didn't).
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
&
th the faulty
> commit log disk, the client continued to write and didn't seem to bother
> (which is what we expected to happen in the first place, but didn't).
>
> From: aaron morton [mailto:aa...@thelastpickle.com]
> Sent: Monday, August 01, 2011 12:19 AM
> To:
Monday, August 01, 2011 12:19 AM
To: user@cassandra.apache.org
Subject: Re: Damaged commit log disk causes Cassandra client to get stuck
A couple of timeouts should have kicked in.
First the rpc_timeout on the server side should have kicked in and given the
client a (thrift) TimedOutException. Se
A couple of timeouts should have kicked in.
First the rpc_timeout on the server side should have kicked in and given the
client a (thrift) TimedOutException. Secondly a client side socket timeout
should be set so the client will timeout the socket. Did either of these appear
in the client side
