You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Gábor Auth <au...@gmail.com> on 2018/05/01 17:40:16 UTC
Re: Schema disagreement
Hi,
On Mon, Apr 30, 2018 at 11:11 PM Gábor Auth <au...@gmail.com> wrote:
> On Mon, Apr 30, 2018 at 11:03 PM Ali Hubail <Al...@petrolink.com>
> wrote:
>
>> What steps have you performed to add the new DC? Have you tried to follow
>> certain procedures like this?
>>
>> https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html
>>
>
> Yes, exactly. :/
>
Okay, removed all new nodes (with `removenode`). Cleared all new node
(removed data and logs).
I did all the steps described in the link (again).
Same result:
Cluster Information:
Name: cluster
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
5de14758-887d-38c1-9105-fc60649b0edf: [new, new, ...]
f4ed784a-174a-38dd-a7e5-55ff6f3002b2: [old, old, ...]
The old nodes try to gossip their own schema:
DEBUG [InternalResponseStage:1] 2018-05-01 17:36:36,266
MigrationManager.java:572 - Gossiping my schema version
f4ed784a-174a-38dd-a7e5-55ff6f3002b2
DEBUG [InternalResponseStage:1] 2018-05-01 17:36:36,863
MigrationManager.java:572 - Gossiping my schema version
f4ed784a-174a-38dd-a7e5-55ff6f3002b2
The new nodes try to gossip their own schema:
DEBUG [InternalResponseStage:4] 2018-05-01 17:36:26,329
MigrationManager.java:572 - Gossiping my schema version
5de14758-887d-38c1-9105-fc60649b0edf
DEBUG [InternalResponseStage:4] 2018-05-01 17:36:27,595
MigrationManager.java:572 - Gossiping my schema version
5de14758-887d-38c1-9105-fc60649b0edf
What can I do? Any suggestion? :(
Bye,
Gábor Auth
Re: Schema disagreement
Posted by Gábor Auth <au...@gmail.com>.
Hi,
On Tue, May 1, 2018 at 10:27 PM Gábor Auth <au...@gmail.com> wrote:
> One or two years ago I've tried the CDC feature but switched off... maybe
> is it a side effect of switched off CDC? How can I fix it? :)
>
Okay, I've worked out. Updated the schema of the affected keyspaces on the
new nodes with 'cdc=false' and everything is okay now.
I think, it is a strange bug around the CDC...
Bye,
Gábor Auth
Re: Schema disagreement
Posted by Gábor Auth <au...@gmail.com>.
Hi,
On Tue, May 1, 2018 at 7:40 PM Gábor Auth <au...@gmail.com> wrote:
> What can I do? Any suggestion? :(
>
Okay, I've diffed the good and the bad system_scheme tables. The only
difference is the `cdc` field in three keyspaces (in `tables` and `views`):
- the value of `cdc` field on the good node is `False`
- the value of `cdc` field on the bad node is `null`
The value of `cdc` field on the other keyspaces is `null`.
One or two years ago I've tried the CDC feature but switched off... maybe
is it a side effect of switched off CDC? How can I fix it? :)
Bye,
Gábor Auth