Re: Schema version mismatch with 3.0.8 and 3.0.14

Generally speaking, I would never advise someone to add nodes to a cluster using a different version than the rest of the cluster. > On Dec 1, 2017, at 11:58 AM, Jai Bheemsen Rao Dhanwada > wrote: > > Thanks Jeff, > > I did some more testing on this version upgrade

Re: Schema version mismatch with 3.0.8 and 3.0.14

Thanks Jeff, I did some more testing on this version upgrade and here is brief summary incase if someone runs into the same issue. Basically, we cannot add new nodes with 3.0.14 or higher version to the cluster with 3.0.8 version of cassandra (haven't tested with 3.0.13) and below are the two

inc repairs aren't updating repairedat timestamp

Hello, I have v3.0.10. Cassandra incremental repair has not been updating the repairedat timestamp on the sstables. Because of this jira : https://issues.apache.org/jira/browse/CASSANDRA-9143. Going back to repair documentation, Datastax now seems to have changed their recommendation from

Re: Node crashes on repair (Cassandra 3.11.1)

Hi Jeff, the repairs worked fine before on version 3.9. I noticed that the validation tasks when doing a repair are not bound anymore to the concurrent_compactors value. Is this maybe too much pressure for the node to manage, so it gets stressed too much? Greetings, Christian Von: Jeff Jirsa