cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lahiru Gamathige <lah...@highfive.com>
Subject Re: native_transport_max_frame_size_in_mb vs max_value_size_in_mb
Date Tue, 01 Nov 2016 18:50:02 GMT
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 ?
>

Mime
View raw message