After a lot of investigation, it seems that the clocks were desynchronized
through the cluster (altough we did not check that resyncing them resolve the
problem, we modify the schma with one node up and restart all other nodes
afterwards).
From: Demeyer
Hello,
I have a cluster running and I'm trying to change the schema on it. Altough it
succeeds on one cluster (a test one), on another it keeps creating two separate
schema versions (both are 2 DC configuration; the cluster where it goes wrong
end up with a schema version on each DC).
I use ap
