On Tue, Feb 15, 2011 at 3:59 AM, Serdar Irmak <sir...@protel.com.tr> wrote:
> Hi, > > > > In a 3 node named (named A,B,C) setup with replication factor 3 and quorum > read/write scenario; > > suppose a new value of data X is written to A and B but not C with any > reason, then A wend down and I fired D with the data of C or with an empty > data where in a case is X is not present in D. > > Then when I read quorum, nodes C and D responded and gave me the old value > (then read repair in background). So doesn’t it mean there is no > constistency with quorum, too ? > > > > > > My best > > Serdar > > > The consistency rules do NOT apply if you introduce a new node without properly bootstrapping it. If you have A,B,C and A fails you should 1) 'nodetool removetoken A'. 2) Start node D with auto_boostrap=true. You can start a node empty (with bootstrap=false) using quorum/quorum, but if you do not 'nodetool repair' it before another node fails you end up with the situation you described. Edward
