Re: unable to repair

Hi Sébastien, The error message you shared came from the repair coordinator node's log, and it's the result of failures reported by 3 other nodes. If you could have a look at the 3 nodes listed in the error message - 135.181.222.100, 135.181.217.109 and 135.181.221.180, you should be able to

Hints not being created

Hey I have a cluster, 3.11.9, in which I am enabling hints, but it appears that no hints are created when other nodes are down. I can see that hints are enabled by running "nodetool statushandoff", and gc_grace_seconds is high enough on all tables, so I'm expecting to see hints being created, since

Re: unable to repair

OK I will check that, thank you! Sébastien Le jeu. 27 mai 2021 à 11:07, Bowen Song a écrit : > Hi Sébastien, > > > The error message you shared came from the repair coordinator node's > log, and it's the result of failures reported by 3 other nodes. If you > could have a look at the 3 nodes lis

Re: Cassandra 4.0 GA

Thank you for the information On Wed, May 26, 2021 at 5:40 PM Kane Wilson wrote: > On Tue, May 25, 2021 at 6:36 AM Jai Bheemsen Rao Dhanwada < > jaibheem...@gmail.com> wrote: > >> Hello All, >> >> I see that Cassandra 4.0 RC1 is released in April, is there going to be >> an official 4.0 GA relea

Re: unable to repair

> > Which client operations could trigger schema change at node level? Do you > mean that for ex creating a new table trigger a schema change globally, not > only at KS/table single level? > Yes, any DDL statement (creating tables, altering, dropping, etc) triggers a schema change across the cluste

Re: Hints not being created

Hey > I have a cluster, 3.11.9, in which I am enabling hints, but it appears > that no hints are created when other nodes are down. > I can see that hints are enabled by running "nodetool statushandoff", and > gc_grace_seconds is high enough on all tables, so I'm expecting to see > hints being crea