Re: Schema version mismatch

changes when there is any schema changes made to the cluster like adding or dropping tables/column/keyspaces i.e CREATE, DROP, ALTER etc. why do we see schema version mismatch other than upgrades time? It can be seen when schema changes are made i.e DDL statements are issues concurrently. If a node

Re: Schema version mismatch

8 at 03:03 Nandakishore Tokala < > nandakishore.tok...@gmail.com> wrote: > >> what is the schema version in Cassandra and for what are all the changes >> schema version is changed? >> >> why do we see schema version mismatch other than upgrades time? >> Can we

Re: Schema version mismatch

for what are all the changes > schema version is changed? > > why do we see schema version mismatch other than upgrades time? > Can we solve the schema version mismatch without restart the > Cassandra nodes > > > > > -- > Thanks & Regards, > Nanda Kishore > --

Schema version mismatch

what is the schema version in Cassandra and for what are all the changes schema version is changed? why do we see schema version mismatch other than upgrades time? Can we solve the schema version mismatch without restart the Cassandra nodes -- Thanks & Regards, Nanda Kishore

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

Re: Schema version mismatch with 3.0.8 and 3.0.14

I guess I didn’t realize you were adding and upgrading s at the same time Do one or the other first (either add the new node at the old version, or upgrade to the new version and then add the new node), or use the two step process described in 13004 -- Jeff Jirsa > On Nov 30, 2017, at 9:40

Re: Schema version mismatch with 3.0.8 and 3.0.14

Hello Jeff, I tried with 3.0.15 as well and I see the same issue. Here are the steps I followed. 1. I have a 3 node C* cluster with 3.0.8 version 2. Added a new node (4th) node with 3.0.15 version of cassandra 3. New node joins the cluster but it is creates it's own schema and don't bootstrap

Re: Schema version mismatch with 3.0.8 and 3.0.14

Yes, going to 3.0.14 or 3.0.15 should work correctly 3.0.15 will have important bug fixes not in 3.0.14 -- Jeff Jirsa > On Nov 29, 2017, at 4:52 PM, Jai Bheemsen Rao Dhanwada > wrote: > > Thanks Jeff, > > You mean if I upgrade from 3.0.8 -> 3.0.15 it should work

Re: Schema version mismatch with 3.0.8 and 3.0.14

Thanks Jeff, You mean if I upgrade from 3.0.8 -> 3.0.15 it should work without any issues? On Wed, Nov 29, 2017 at 4:21 PM, Jeff Jirsa wrote: > This is because in 3.0.14, we had to bump the internode messaging version > to fix a nasty bug (it's something we almost never do in

Re: Schema version mismatch with 3.0.8 and 3.0.14

This is because in 3.0.14, we had to bump the internode messaging version to fix a nasty bug (it's something we almost never do in minor versions, but it was necessary here), and schema changes won't cross internode messaging versions. You can continue upgrading, and when new nodes reach 3.0.14

Schema version mismatch with 3.0.8 and 3.0.14

Hello, I am trying to upgrade the cassandra version from the 3.0.8 to 3.0.14. I am adding a new node with 3.0.14 version to 3.0.8. cluster and I see the schema disagreement between the nodes and the new node doesn't stream any data. I am looking at :

Re: Cassandra Schema version mismatch

gt; On May 5, 2017, at 3:17 PM, Jeff Jirsa <jji...@apache.org > >> <mailto:jji...@apache.org>> wrote: > >> > >> > >> > >>> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com > >>> <mailto:ni...@bamlabs.com&

Re: Cassandra Schema version mismatch

ojo.me> > wrote: > > > > 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 <jji...@apache.org> wrote: > >> > >> > >> > >>>

Re: Cassandra Schema version mismatch

t; > Sent from my iPhone > >> On May 5, 2017, at 3:17 PM, Jeff Jirsa <jji...@apache.org> wrote: >> >> >> >>> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote: >>> Hi Experts, >>> >>> We foun

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 <jji...@apache.org> wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote: >> Hi Experts, >>

Re: Cassandra Schema version mismatch

upgraded long back. > > Sent from my iPhone > > > On May 5, 2017, at 5:17 PM, Jeff Jirsa <jji...@apache.org> wrote: > > > > > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote: > >> Hi Experts, > >>

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 <jji...@apache.org> wrote: > > > >> On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> wrote: >> Hi Exp

Re: Cassandra Schema version mismatch

On 2017-05-05 11:00 (-0700), Nitan Kainth <ni...@bamlabs.com> 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

Re: Cassandra Schema version mismatch

ythian.com > >> On Fri, May 5, 2017 at 7:00 PM, Nitan Kainth <ni...@bamlabs.com> 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 th

Re: Cassandra Schema version mismatch

: @cjrolo | Skype: cjr2k3 | Linkedin: *linkedin.com/in/carlosjuzarterolo <http://linkedin.com/in/carlosjuzarterolo>* Mobile: +351 918 918 100 www.pythian.com On Fri, May 5, 2017 at 7:00 PM, Nitan Kainth <ni...@bamlabs.com> wrote: > Hi Experts, > > We found schema version mismat

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