; two racks while in other locations we use three, the replication factor
> however for all keyspaces remains the same – 3 for all user defined
> keyspaces. Maybe this is something that could cause issues with duplicates?
> It's
> a theoretical but cassandra having to place two rep
cluster. I’m afraid we cannot provide you with the info
you’ve requested.
Gediminas
From: João Reis
Sent: Tuesday, May 12, 2020 19:58
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Re: Adding new DC results in clients failing to connect
Unfortunately I'm not able to reproduce this.
ra having to place two replicas on the same rack
> maybe placed both the primary and a backup replica on the same node. Hence
> a duplicate...
>
>
>
> Gediminas
>
>
>
> *From:* João Reis
> *Sent:* Thursday, May 7, 2020 19:22
> *To:* user@cassandra.apache.org
>
r@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: RE: [EXTERNAL] Re: Adding new DC results in clients failing to connect
Hello,
Thanks for the reply.
Following your advice we took a look at system.local for seed nodes and
compared that data with nodetool ring. Both sources con
t;
>
>
> null
>
> null
>
> 192.168.104.111
>
> null
>
> null
>
> null
>
> null
>
> null
>
>
>
> Have a wonderful day 😊
>
>
>
> Gediminas
>
>
>
>
@cassandra.apache.org
Subject: RE: [EXTERNAL] Re: Adding new DC results in clients failing to connect
Hello,
Thanks for the reply.
Following your advice we took a look at system.local for seed nodes and
compared that data with nodetool ring. Both sources contain the same tokens for
these specific hosts. Will
Hello,
Thanks for the reply.
Following your advice we took a look at system.local for seed nodes and
compared that data with nodetool ring. Both sources contain the same tokens for
these specific hosts. Will continue looking into system.peers.
We have enabled more verbosity on the C# driver an
