?
From: Sartor Fabien (DIN) via user
Sent: 09 April 2025 13:50
To: user@cassandra.apache.org
Cc: Sartor Fabien (DIN)
Subject: RE: Schema Version Mismatch issue
EXTERNAL EMAIL - USE CAUTION when clicking links or attachments
Hi Soyal,
I have encountered similar issues in the
Hi Soyal,
I have encountered similar issues in the past. What has consistently worked for
me is performing a rolling restart of all nodes. If you don’t have tools like
Ansible or scripts to automate the process, I suggest starting by restarting
the node with the problematic schema. That might h
FYI
this is the info I got after research on schema version
what is the schema version in Cassandra and for what are all the changes
schema version is changed?
schema version is a UUID used to set a baseline version of the schema. It
tracks if a schema migration is required. Schema version chang
Thanks Justin
On Thu, Jun 7, 2018 at 4:27 PM, Justin Cameron
wrote:
> You may run into schema mismatch issues if you make multiple schema
> alterations in a very short period of time (e.g. if you're programmatically
> modifying tables 50x a second). You'll be better off making schema changes
> i
You may run into schema mismatch issues if you make multiple schema
alterations in a very short period of time (e.g. if you're programmatically
modifying tables 50x a second). You'll be better off making schema changes
in advance. If you need to make dynamic changes then you could check the
version
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
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
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
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
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?
>
>>
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,
>
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
12 matches
Mail list logo
