Cheng, as far as I remember, CASSANDRA-18291 was a fix for a problem we
noticed with a driver which could result in noticing the updated schema
version before it was applied.
It should be easy to implement a jvm-dtest for the problem you mentioned -
would like to provide such a test?
Thanks
- - -
And it seems that the main fix for the
https://issues.apache.org/jira/browse/CASSANDRA-18291 is to change the
order of updating the schema version in the system.local table.
Before the patch, it was at the beginning of
the Schema::mergeAndUpdateVersion(), vs. with the patch, it is moved to the
end
Thanks Jacek,
In our C* version 4.1.1.1 we have your change
https://issues.apache.org/jira/browse/CASSANDRA-17044
However, I noticed that you had another fix
https://issues.apache.org/jira/browse/CASSANDRA-18291 that we didn't pick
up yet.
Do you think it might be the cause? Could you elaborate a
Please cc me when you create a ticket
pon., 1 kwi 2024, 14:13 użytkownik Bowen Song via dev <
dev@cassandra.apache.org> napisał:
> It sounds worthy of a Jira ticket.
>
> On 01/04/2024 06:23, Cheng Wang via dev wrote:
> > Hello,
> >
> > I have recently encountered a problem concerning schema disag
Agreed. I will cut a JIRA ticket. If anyone has seen the similar issues
pls let me know.
We have seen something similar e.g. sometimes we still see the nodes that
are no longer in the ring with UNREACHABLE when I do describecluster.
Cheng
On Mon, Apr 1, 2024 at 5:12 AM Bowen Song via dev
wrote:
It sounds worthy of a Jira ticket.
On 01/04/2024 06:23, Cheng Wang via dev wrote:
Hello,
I have recently encountered a problem concerning schema disagreement
in Cassandra 4.1. It appears that the schema versions do not reconcile
as expected.
The issue can be reproduced by following these st
Hello,
I have recently encountered a problem concerning schema disagreement in
Cassandra 4.1. It appears that the schema versions do not reconcile as
expected.
The issue can be reproduced by following these steps:
- Disable the gossip in Node A.
- Make a schema change in Node B, such as creating
