consistency level definition should be a definition of requirement from the application perspective, it should not be tied to some ephemeral state in the system (: a node being deemed "available/up" or down is determined by the gossip and changes every second )
what you want can be simply achieved by CL=ALL and then modifying current read result to not return failure, but return the "best effort" result obtained so far --- although that will need you to wait for a slightly longer time On Thu, Jun 16, 2011 at 9:46 AM, AJ <a...@dude.podzone.net> wrote: > On 6/16/2011 10:05 AM, Ryan King wrote: > >> >> I don't think this buys you anything that you can't get with quorum >> reads and writes. >> >> -ryan >> >> > QUORUM <= ALL_AVAIL <= ALL == RF >
