Re: Lost MUTATIONS on several Cassandra nodes - no impact on the client

[ruslan usifov]

On Sun, Jan 23, 2011 at 6:30 AM, ruslan usifov <ruslan.usi...@gmail.com>
> wrote:
>
> 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.
>
>
Is it possible to detect that write doesn't happen anywhere? Or it is only
possible detect consistency failure?