Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-12-01 Thread Jon Haddad
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 and here is brief summary

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-12-01 Thread Jai Bheemsen Rao Dhanwada
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 opt

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-11-30 Thread Jeff Jirsa
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 A

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-11-30 Thread Jai Bheemsen Rao Dhanwada
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 an

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-11-29 Thread Jeff Jirsa
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 without any issues? > >>

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-11-29 Thread Jai Bheemsen Rao Dhanwada
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 minor versions, >

Re: Schema version mismatch with 3.0.8 and 3.0.14

2017-11-29 Thread Jeff Jirsa
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 th

Schema version mismatch with 3.0.8 and 3.0.14

2017-11-29 Thread Jai Bheemsen Rao Dhanwada
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 : https://issues.apache.org/jira/browse/CASSAN