Thanks Erick!
On Thu, Jul 22, 2021 at 2:29 PM Erick Ramirez
wrote:
> I wouldn't use either of the steps you outlined. Neither of them are
> correct.
>
> Follow the procedure documented here instead --
> https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/operations/opsAddDCToCluster.html.
>
I wouldn't use either of the steps you outlined. Neither of them are
correct.
Follow the procedure documented here instead --
https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/operations/opsAddDCToCluster.html.
Cheers!
; 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
>
t's 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: Add
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
iminas
From: Jorge Bay Gondra
Sent: Thursday, April 30, 2020 11:45
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Adding new DC results in clients failing to connect
Hi,
You can enable logging at driver to see what's happening under the hood:
https://docs.datastax.com/en/developer/cs
Hi,
You can enable logging at driver to see what's happening under the hood:
https://docs.datastax.com/en/developer/csharp-driver/3.14/faq/#how-can-i-enable-logging-in-the-driver
With logging information, it should be easy to track the issue down.
Can you query system.local and system.peers on a s
I agree with Jeff here: It's not recommended to do that but it should be
still fine :).
Something that might be slightly safer (even though 3.11.0 is buggy as
mentioned above...) could be to add a 3.11.0 cluster. Do the streaming with
3.11.0, upgrade the new DC only, switch clients over, terminate
Thanks Jeff,
We want to migrate to Apache 3.11.3 once entire cluster in apache we
eventually decommission datastax DC
On Mon, Jul 1, 2019, 9:31 AM Jeff Jirsa wrote:
> Should be fine, but you probably want to upgrade anyway, there were a few
> really important bugs fixed since 3.11.0
>
> > On Ju
Should be fine, but you probably want to upgrade anyway, there were a few
really important bugs fixed since 3.11.0
> On Jul 1, 2019, at 3:25 AM, Rahul Reddy wrote:
>
> Hello All,
>
> We have datastax Cassandra cluster which uses 3.11.0 and we want to add new
> DC with apache Cassandra 3.11.3.
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
[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 g
...@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, Ke
t;
> 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?
>
>
>
>
>
> On 13 Mar
enneth 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 2018 a
] RE: Adding new DC?
On 13 March 2018 at 03:28, Kenneth Brotman wrote:
You can’t migrate and upgrade at the same time perhaps but you could do one and
then the other so as to end up on new version. I’m guessing it’s an error in
the yaml file or a port not open. Is there any good reason
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?
>
>
>
> Yo
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 wrote:
You cannot migrate and upgrade at the same time across major versions.
Streaming is (usually) not compatible between versions.
I'
> lord of the (C*) rings (Staff Systems Engineer – Cassandra)
>
> *From:* Kunal Gangakhedkar [mailto:kgangakhed...@gmail.com]
> *Sent:* Sunday, March 11, 2018 10:20 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] RE: Adding new DC?
>
>
>
> Hi Kenneth,
&
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
@cassandra.apache.org
Subject: [EXTERNAL] RE: Adding new DC?
Hi Kenneth,
Replies inline below.
On 12-Mar-2018 3:40 AM, "Kenneth Brotman"
mailto:kenbrot...@yahoo.com.invalid>> wrote:
Hi Kunal,
That version of Cassandra is too far before me so I’ll let others answer. I
was wonder why you wouldn’
How did you distribute your seed nodes across whole cluster?
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Mar 12, 2018, 5:12 AM -0400, Oleksandr Shulgin
, wrote:
> > On Sun, Mar 11, 2018 at 10:31 PM, Kunal Gangakhedkar
> > wrote:
> > > Hi all,
> > >
> > > We currently have a clust
On Sun, Mar 11, 2018 at 10:31 PM, Kunal Gangakhedkar <
kgangakhed...@gmail.com> wrote:
> Hi all,
>
> We currently have a cluster in GCE for one of the customers.
> They want it to be migrated to AWS.
>
> I have setup one node in AWS to join into the cluster by following:
> https://docs.datastax.co
Hi Kenneth,
Replies inline below.
On 12-Mar-2018 3:40 AM, "Kenneth Brotman"
wrote:
Hi Kunal,
That version of Cassandra is too far before me so I’ll let others answer.
I was wonder why you wouldn’t want to end up on 3.0x if you’re going
through all the trouble of migrating anyway?
Applica
Hi Kunal,
That version of Cassandra is too far before me so I’ll let others answer. I
was wonder why you wouldn’t want to end up on 3.0x if you’re going through all
the trouble of migrating anyway?
Are both data centers in the same region on AWS? Can you provide yaml file for
us to s
28 matches
Mail list logo
