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: <CABAWSr7zSA7-fx1BYKbQGNtWy0mfEDYEtV8ZAAh0J4Ym9Aqweg@mail.gmail.com>
References: <CABAWSr7zSA7-fx1BYKbQGNtWy0mfEDYEtV8ZAAh0J4Ym9Aqweg@mail.gmail.com>
From: Lahiru Gamathige <lahiru@highfive.com>
Date: Tue, 1 Nov 2016 11:50:02 -0700
Message-ID: <CABAWSr6Y+KcSPHhPi-_RyQvAvbtQK7oqX6uUmhEnhren-N1ADQ@mail.gmail.com>
Subject: Re: native_transport_max_frame_size_in_mb vs max_value_size_in_mb
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113dab16ca7f0a054041ca83
archived-at: Tue, 01 Nov 2016 18:50:19 -0000

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

Since this is already commented this size check is disabled or its default
set to 256MB and if we have higher sized SSTables those are going to mark
currupted ?

On Tue, Nov 1, 2016 at 11:47 AM, Lahiru Gamathige <lahiru@highfive.com>
wrote:

> Hi Users,
>
> I see that C* introduced max_value_size_in_mb and if a SSTable is larger
> than this it will be a currupted SSTable. In our current cluster I see
> tables with very large SSTables, and if we are migrating to new version
> should I increase this number ?
>
> But increasing max_value_size_in_mb to a higher value looks risky but the
> documentation says these should match.
>
> Any thoughts ?
>

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

<div dir=3D"ltr">Since this is already commented this size check is disable=
d or its default set to 256MB and if we have higher sized SSTables those ar=
e going to mark currupted ?</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Nov 1, 2016 at 11:47 AM, Lahiru Gamathige <span di=
r=3D"ltr">&lt;<a href=3D"mailto:lahiru@highfive.com" target=3D"_blank">lahi=
ru@highfive.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"><di=
v dir=3D"ltr">Hi Users,<div><br></div><div>I see that C* introduced=C2=A0ma=
x_value_size_in_<wbr>mb and if a SSTable is larger than this it will be a c=
urrupted SSTable. In our current cluster I see tables with very large SSTab=
les, and if we are migrating to new version should I increase this number ?=
</div><div><br></div><div>But increasing max_value_size_in_mb to a higher v=
alue looks risky but the documentation says these should match.=C2=A0</div>=
<div><br></div><div>Any thoughts ?</div></div>
</blockquote></div><br></div>

--001a113dab16ca7f0a054041ca83--