Re: Cassandra Schema version mismatch

Yes Carlos same issue in our case. We had some cloud issue and node wasn’t marked down. We did have some schema changes a few days back but didn’t notice because one node was still serving and when that stopped serving, we saw issues. So, it WAS due to schema changes that happened few days back

Re: Cassandra Schema version mismatch

Sometimes "resetlocalschema" (happened to me, didn't check why) will not work, and you need to stop the offending nodes and bring them back one by one.. That solved the issue. In the cases I've seen this happened the clusters in question where either: a) A couple of nodes down (cloud provider

Re: Cassandra Schema version mismatch

Thank you Jeff. James, We started getting insufficient replica errors. Cqlsh stopped working for two nodes . Sent from my iPhone > On May 5, 2017, at 7:13 PM, James Rothering wrote: > > I've heard about this ... how did the problem present itself? > > Sent from my

Re: Cassandra Schema version mismatch

I've heard about this ... how did the problem present itself? Sent from my iPhone > On May 5, 2017, at 3:17 PM, Jeff Jirsa wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: >> Hi Experts, >> >> We found schema version mismatch in our

Re: Cassandra Schema version mismatch

Generally shouldn't happen in most modern versions of cassandra. Could be simultaneous conflicting statements (two "CREATE TABLE" statements at the same time, which can happen with programatic schema changes), or unhealthy schema tables (lots and lots of changes create tombstones in the schema

Re: Cassandra Schema version mismatch

No, just two nodes have mismatch out of 18 nodes. We upgraded long back. Sent from my iPhone > On May 5, 2017, at 5:17 PM, Jeff Jirsa wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: >> Hi Experts, >> >> We found schema version

Re: Cassandra Schema version mismatch

On 2017-05-05 11:00 (-0700), Nitan Kainth wrote: > Hi Experts, > > We found schema version mismatch in our cluster. We fixed it by bouncing C* > on nodes where version was mismatched. Can someone suggest, what are the > possible reasons for this? We are trying to figure

Re: Cassandra Schema version mismatch

No schematic change! Sent from my iPhone > On May 5, 2017, at 2:30 PM, Carlos Rolo wrote: > > Are you changing the schema in a dynamic fashion? If you get problems > (network, gc pauses, etc) during the schema changes it might lead to that. > > Regards, > > Carlos Juzarte

Re: Cassandra Schema version mismatch

Are you changing the schema in a dynamic fashion? If you get problems (network, gc pauses, etc) during the schema changes it might lead to that. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter:

Cassandra Schema version mismatch

Hi Experts, We found schema version mismatch in our cluster. We fixed it by bouncing C* on nodes where version was mismatched. Can someone suggest, what are the possible reasons for this? We are trying to figure out the root cause. thank you!