Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAORswtwDVEd5m9YQj7yA0w8aR0BQn68tFnQJHutYHKJAYGpFuQ@mail.gmail.com>
References: 
 <CAF_ijK+mAsLkAGN+t1BJyM4D=3RcYhBUV8MwvpXgG0+VPjUUrQ@mail.gmail.com>
	<CAORswtwDVEd5m9YQj7yA0w8aR0BQn68tFnQJHutYHKJAYGpFuQ@mail.gmail.com>
Date: Thu, 5 Nov 2015 18:36:00 +0200
Message-ID: 
 <CAF_ijKJxLWqRMgusMdUY4G01imtGvrHLyg7UmDSiS0gyA0qnvg@mail.gmail.com>
Subject: Re: Replication Factor Change
From: Yulian Oifa <oifa.yulian@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a114b3774db41a80523cdb874

--001a114b3774db41a80523cdb874
Content-Type: text/plain; charset=UTF-8

Hello
OK i got it , so i should set CL to ALL for reads, otherwise data may be
retrieved from nodes that does not have yet current record.
Thanks for help.
Yulian Oifa

On Thu, Nov 5, 2015 at 5:33 PM, Eric Stevens <mightye@gmail.com> wrote:

> If you switch reads to CL=LOCAL_ALL, you should be able to increase RF,
> then run repair, and after repair is complete, go back to your old
> consistency level.  However, while you're operating at ALL consistency, you
> have no tolerance for a node failure (but at RF=1 you already have no
> tolerance for a node failure, so that doesn't really change your
> availability model).
>
> On Thu, Nov 5, 2015 at 8:01 AM Yulian Oifa <oifa.yulian@gmail.com> wrote:
>
>> Hello to all.
>> I am planning to change replication factor from 1 to 3.
>> Will it cause data read errors in time of nodes repair?
>>
>> Best regards
>> Yulian Oifa
>>
>

--001a114b3774db41a80523cdb874
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hello <br></div>OK i got it , so i should set CL=
 to ALL for reads, otherwise data may be retrieved from nodes that does not=
 have yet current record.<br></div><div>Thanks for help.<br></div><div>Yuli=
an Oifa<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Thu, Nov 5, 2015 at 5:33 PM, Eric Stevens <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:mightye@gmail.com" target=3D"_blank">mightye@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">If you=
 switch reads to CL=3DLOCAL_ALL, you should be able to increase RF, then ru=
n repair, and after repair is complete, go back to your old consistency lev=
el.=C2=A0 However, while you&#39;re operating at ALL consistency, you have =
no tolerance for a node failure (but at RF=3D1 you already have no toleranc=
e for a node failure, so that doesn&#39;t really change your availability m=
odel). =C2=A0</div><div class=3D"HOEnZb"><div class=3D"h5"><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Thu, Nov 5, 2015 at 8:01 AM Yulian Oif=
a &lt;<a href=3D"mailto:oifa.yulian@gmail.com" target=3D"_blank">oifa.yulia=
n@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><div><div><div>Hello to all.<br></div>I am planning to change=
 replication factor from 1 to 3.<br></div>Will it cause data read errors in=
 time of nodes repair?<br><br></div>Best regards<br></div></div><div dir=3D=
"ltr">Yulian Oifa<br></div></blockquote></div>
</div></div></blockquote></div><br></div>

--001a114b3774db41a80523cdb874--