Re: [EXTERNAL] Re: Adding new DC results in clients failing to connect

le 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 replicas on the same

RE: [EXTERNAL] Re: Adding new DC results in clients failing to connect

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. Would

Re: [EXTERNAL] Re: Adding new DC results in clients failing to connect

ace 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 > *Subject:* Re

RE: [EXTERNAL] Re: Adding new DC results in clients failing to connect

a theoretical but cassandra 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 Subject: Re: [EXTERNAL] Re: Adding new DC

Re: [EXTERNAL] Re: Adding new DC results in clients failing to connect

gt; null > > null > > 192.168.104.111 > > null > > null > > null > > null > > null > > > > Have a wonderful day  > > > > Gediminas > > > > *From:* Gedim

RE: [EXTERNAL] Re: Adding new DC results in clients failing to connect

@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

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 continue looking into system.peers. We have enabled more verbosity on the C# driver

RE: [EXTERNAL] RE: Adding new DC?

previous replies if you’re doing that. Let us know your results. Kenneth Brotman From: Kenneth Brotman [mailto:kenbrot...@yahoo.com] Sent: Monday, March 12, 2018 7:14 PM To: 'user@cassandra.apache.org' Subject: RE: [EXTERNAL] RE: Adding new DC? Kunal, Sorry for asking you things

RE: [EXTERNAL] RE: Adding new DC?

[mailto:kenbrot...@yahoo.com] Sent: Monday, March 12, 2018 7:14 PM To: 'user@cassandra.apache.org' Subject: RE: [EXTERNAL] RE: Adding new DC? Kunal, Sorry for asking you things you already answered. You provided a lot of good information and you know what you’re are doing. It’s going

RE: [EXTERNAL] RE: Adding new DC?

...@gmail.com] Sent: Monday, March 12, 2018 4:43 PM To: user@cassandra.apache.org Cc: Nikhil Soman Subject: Re: [EXTERNAL] RE: Adding new DC? Yes, that's correct. The customer wants us to migrate the cassandra setup in their AWS account. Thanks, Kunal On 13 March 2018 at 04:56, Kenneth

Re: [EXTERNAL] RE: Adding new DC?

ogle and one on Amazon? > > > > Kenneth Brotman > > > > *From:* Kunal Gangakhedkar [mailto:kgangakhed...@gmail.com] > *Sent:* Monday, March 12, 2018 4:24 PM > *To:* user@cassandra.apache.org > *Cc:* Nikhil Soman > *Subject:* Re: [EXTERNAL] RE: Adding new DC? > &

Re: [EXTERNAL] RE: Adding new DC?

t; > Kenneth Brotman > > > > *From:* Kunal Gangakhedkar [mailto:kgangakhed...@gmail.com] > *Sent:* Monday, March 12, 2018 4:13 PM > *To:* user@cassandra.apache.org > *Cc:* Nikhil Soman > *Subject:* Re: [EXTERNAL] RE: Adding new DC? > > > > > > On 13 March 2

RE: [EXTERNAL] RE: Adding new DC?

t. Hence sticking to 2.1.x for now. And, so far, 2.1.x has been serving the purpose. Kunal Kenneth Brotman From: Durity, Sean R [mailto:sean_r_dur...@homedepot.com] Sent: Monday, March 12, 2018 11:36 AM To: user@cassandra.apache.org Subject: RE: [EXTERNAL] RE: Adding new DC? Y

Re: [EXTERNAL] RE: Adding new DC?

now. And, so far, 2.1.x has been serving the purpose. Kunal > > Kenneth Brotman > > > > *From:* Durity, Sean R [mailto:sean_r_dur...@homedepot.com] > *Sent:* Monday, March 12, 2018 11:36 AM > *To:* user@cassandra.apache.org > *Subject:* RE: [EXTERNAL] RE: Ad

RE: [EXTERNAL] RE: Adding new DC?

4:13 PM To: user@cassandra.apache.org Cc: Nikhil Soman Subject: Re: [EXTERNAL] RE: Adding new DC? On 13 March 2018 at 00:06, Durity, Sean R <sean_r_dur...@homedepot.com> wrote: You cannot migrate and upgrade at the same time across major versions. Streaming is (usually) not comp

Re: [EXTERNAL] RE: Adding new DC?

On 13 March 2018 at 00:06, Durity, Sean R wrote: > You cannot migrate and upgrade at the same time across major versions. > Streaming is (usually) not compatible between versions. > I'm not trying to upgrade as of now - first priority is the migration. We can look

RE: [EXTERNAL] RE: Adding new DC?

From: Durity, Sean R [mailto:sean_r_dur...@homedepot.com] Sent: Monday, March 12, 2018 11:36 AM To: user@cassandra.apache.org Subject: RE: [EXTERNAL] RE: Adding new DC? You cannot migrate and upgrade at the same time across major versions. Streaming is (usually) not compatible between

RE: [EXTERNAL] RE: Adding new DC?

You cannot migrate and upgrade at the same time across major versions. Streaming is (usually) not compatible between versions. As to the migration question, I would expect that you may need to put the external-facing ip addresses in several places in the cassandra.yaml file. And, yes, it would