Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Date: Sat, 19 Aug 2017 22:45:21 +0000 (UTC)
From: Sotirios Delimanolis <sotodel_89@yahoo.com.INVALID>
To: <user@cassandra.apache.org>
Message-ID: <1643503889.885896.1503182721343@mail.yahoo.com>
In-Reply-To: <CAPbVhuODmKJkG9=Pk0vGjCCrGzZQz90tfSaTBR+ejag+o63ZMA@mail.gmail.com>
References: <842359409.565887.1503097548174.ref@mail.yahoo.com> <842359409.565887.1503097548174@mail.yahoo.com> <CAPbVhuMvWyfYL3a-sJuCuktqbj9GpBBfJWarMnLKcJ3+ogJSTg@mail.gmail.com> <CAPbVhuPoCrj2z2hwA7r+EUkWHr0pJ8AG0Cw_aGV9V6pAvbLU7A@mail.gmail.com> <CAPbVhuMZ226M+544-5ouBGwwX8yC1bt7RBnMBQagKQX4nJwakA@mail.gmail.com> <CAPbVhuNU4LJyK18gpGFYFDxfqjNXLd_j9cSE3-8GXB85EU6uHw@mail.gmail.com> <CAPbVhuODmKJkG9=Pk0vGjCCrGzZQz90tfSaTBR+ejag+o63ZMA@mail.gmail.com>
Subject: Re: Moving all LCS SSTables to a repaired state
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_885895_1175814748.1503182721342"
archived-at: Sat, 19 Aug 2017 22:45:51 -0000

------=_Part_885895_1175814748.1503182721342
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

That's the only way to get this done then, break writes and fix them with incremental repairs?

On Friday, August 18, 2017, 5:17:38 PM PDT, kurt greaves <kurt@instaclustr.com> wrote:

You need to run an incremental repair for sstables to be marked repaired. However only if all of the data in that Sstable is repaired during the repair will you end up with it being marked repaired, otherwise an anticompaction will occur and split the unrepaired data into its own sstable.It's pretty unlikely you will get all SSTables marked as repaired unless you stop writing data and run inc repair multiple times.
------=_Part_885895_1175814748.1503182721342
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"font-family:courier new, courier, mo=
naco, monospace, sans-serif;font-size:16px;"><div><div>That's the only way =
to get this done then, break writes and fix them with incremental repairs?<=
/div></div><div><br></div><div><br></div><div id=3D"yahoo_quoted_3539925844=
" class=3D"yahoo_quoted"><div style=3D"font-family:'Helvetica Neue', Helvet=
ica, Arial, sans-serif;font-size:13px;color:#26282a;"><div>On Friday, Augus=
t 18, 2017, 5:17:38 PM PDT, kurt greaves &lt;kurt@instaclustr.com&gt; wrote=
:</div><div><br></div><div><br></div><div><div id=3D"yiv5626884877"><div>Yo=
u need to run an incremental repair for sstables to be marked repaired. How=
ever only if all of the data in that Sstable is repaired during the repair =
will you end up with it being marked repaired, otherwise an anticompaction =
will occur and split the unrepaired data into its own sstable.<div>It&#39;s=
 pretty unlikely you will get all SSTables marked as repaired unless you st=
op writing data and run inc repair multiple times.</div></div></div></div><=
/div></div></div></body></html>
------=_Part_885895_1175814748.1503182721342--