But you can not depend on such behavior. If you do a write and you get an unavailable exception, the only thing you know is at that time it was not able to be placed on all the nodes required to meet your CL. It may eventually end up on all those nodes, it may not be on any of the nodes or at the time you read the reply it could be on some subset of the nodes. Regardless of the outcome, it is safe to retry.
On Tue, Feb 15, 2011 at 2:00 PM, Aaron Morton <aa...@thelastpickle.com>wrote: > The write will not start if there are insufficient nodes up. In this case > (All cl) you would get an error and nothing would be committed to disk. You > would get an Unavailable exception. > > Aaron > > On 16/02/2011, at 7:46 AM, Thibaut Britz <thibaut.br...@trendiction.com> > wrote: > > > Your write will fail. But if the write has reached at least one node, > > it will eventually reach all the other nodes as well. So it won't > > rollback. > > > > > > On Tue, Feb 15, 2011 at 7:38 PM, A J <s5a...@gmail.com> wrote: > >> Say I set write consistency level to ALL and all but one node are down. > What > >> happens to writes ? Does it rollback from the live node before returning > >> failure to client ? > >> Thanks. >
