Got it!
Thanks a lot Jeff :)
https://issues.apache.org/jira/browse/CASSANDRA-14672 is almost certainly
due to pre-existing corruption . That the user is seeing 14672 is due to
extra guards added in 3.11.3, but 14672 isn't likely going to hit you
unless you're subject to
https://issues.apache.org/jira/browse/CASSANDRA-14515 , w
Any opinion please ?
Le jeu. 6 sept. 2018 à 22:18, Ahmed Eljami a
écrit :
> Hi,
>
> We are testing Cassandra 3.11.2 and we sawed that it contains a critcal
> bug wich was fixed in 3.11.3 (
> https://issues.apache.org/jira/browse/CASSANDRA-13929).
>
> After about 1 months of testing, we haven't
Hi,
We are testing Cassandra 3.11.2 and we sawed that it contains a critcal
bug wich was fixed in 3.11.3 (
https://issues.apache.org/jira/browse/CASSANDRA-13929).
After about 1 months of testing, we haven't encountered this bug in our
environnement, but to be sure before going in production, we
