cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: Lost MUTATIONS on several Cassandra nodes - no impact on the client
Date Sun, 23 Jan 2011 14:35:03 GMT
On Sun, Jan 23, 2011 at 6:30 AM, ruslan usifov <ruslan.usifov@gmail.com> wrote:
>
>
> 2011/1/20 Jonathan Ellis <jbellis@gmail.com>
>>
>> It guarantees that if the requested ConsistencyLevel is not achieved,
>> client will get a TimedOutException, which is a signal you need to add
>> capacity to handle what you are throwing at the cluster.
>>
> Sorry and when UnavailableException is thows? When data can't be saved
> anywhere?
>

Right. The difference is that the gossip process builds a topology of
UP/DOWN hosts so Unavailable is thrown quickly. If you need ALL and
one replica is known down -> Unavailable.

However if the coordinator believe the node was UP and the request
took longer then RCPTimeout (default 10,000,000 ms) ->
TimedOutException

Mime
View raw message