RE: Data is not syncing up when we add one more Node(DR) to existing 3 node cluster
Hi John,
Yes!
Regards,
Anil Ganipineni
Adaequare GSP<http://www.adaequare.com/ugsp/>
GSP Support : 040 660 335 88
Personal : +91 96522 314 80
P Please consider environment before printing this page.
From: John Belliveau
Sent: 13 December 2019 06:31
To: user@cassandra.apache.org
Subject: Re: Data is not syncing up when we add one more Node(DR) to existing 3
node cluster
**CAUTION: This email is originated from outside the organization. Be cautious
before opening the link or attachments. Please verify the email id and source
of the sender.**
Hi Anil,
In the cassandra.yaml file on your new node in DC2, is the IP address for the
seeds set to the seed node in DC1?
Best,
John
On Wed, Dec 11, 2019 at 11:09 PM Anil Kumar Ganipineni
mailto:akganipin...@adaequare.com>> wrote:
Hi All,
We have 3 node cluster on datacentre DC1 and below is our key space
declaration. The current data size on the cluster is ~10GB. When we add a new
node on datacentre DC2, the new node is not syncing up with the data, but it is
showing UN when I run the nodetool status.
CREATE KEYSPACE production WITH REPLICATION = { 'class' :
'org.apache.cassandra.locator.NetworkTopologyStrategy', 'DC1': '3', 'DC2': '1'
} AND DURABLE_WRITES = true;
Please provide suggestions to make the new node on DC2 to sync up with existing
cluster. This is required as the DC2 is our DR in a different region other than
existing cluster.
Regards,
Anil Ganipineni
P Please consider environment before printing this page.
Re: Data is not syncing up when we add one more Node(DR) to existing 3 node cluster
Hi Anil,
In the cassandra.yaml file on your new node in DC2, is the IP address for
the seeds set to the seed node in DC1?
Best,
John
On Wed, Dec 11, 2019 at 11:09 PM Anil Kumar Ganipineni <
akganipin...@adaequare.com> wrote:
> Hi All,
>
>
>
> We have 3 node cluster on datacentre DC1 and below is our key space
> declaration. The current data size on the cluster is ~10GB. When we add a
> new node on datacentre DC2, the new node is not syncing up with the data,
> but it is showing UN when I run the *nodetool status*.
>
>
>
> *CREATE* KEYSPACE *production* *WITH* REPLICATION = { 'class' :
> 'org.apache.cassandra.locator.NetworkTopologyStrategy', 'DC1': '3', 'DC2':
> '1' } *AND* DURABLE_WRITES = *true*;
>
>
>
>
>
> Please provide suggestions to make the new node on DC2 to sync up with
> existing cluster. This is required as the DC2 is our DR in a different
> region other than existing cluster.
>
>
>
>
>
> *Regards,*
>
> *Anil Ganipineni*
>
>
>
> *P** Please consider environment before printing this page.*
>
>
>
RE: Data is not syncing up when we add one more Node(DR) to existing 3 node cluster
Hi Raman,
Thanks for the response.
I will try and let you know the status. We have to do it on production
environment, so might be it will take time to proceed.
Regards,
Anil Ganipineni
P Please consider environment before printing this page.
From: raman gugnani
Sent: 12 December 2019 09:49
To: user@cassandra.apache.org
Subject: Re: Data is not syncing up when we add one more Node(DR) to existing 3
node cluster
**CAUTION: This email is originated from outside the organization. Be cautious
before opening the link or attachments. Please verify the email id and source
of the sender.**
HI Anil,
Please follow the below link.
https://thelastpickle.com/blog/2019/02/26/data-center-switch.html
Did you ran the command nodetool rebuild old_dc_name to stream the old
historical data to new data center.
Step 9 of the above article.
On Thu, 12 Dec 2019 at 09:39, Anil Kumar Ganipineni
mailto:akganipin...@adaequare.com>> wrote:
Hi All,
We have 3 node cluster on datacentre DC1 and below is our key space
declaration. The current data size on the cluster is ~10GB. When we add a new
node on datacentre DC2, the new node is not syncing up with the data, but it is
showing UN when I run the nodetool status.
CREATE KEYSPACE production WITH REPLICATION = { 'class' :
'org.apache.cassandra.locator.NetworkTopologyStrategy', 'DC1': '3', 'DC2': '1'
} AND DURABLE_WRITES = true;
Please provide suggestions to make the new node on DC2 to sync up with existing
cluster. This is required as the DC2 is our DR in a different region other than
existing cluster.
Regards,
Anil Ganipineni
P Please consider environment before printing this page.
--
Raman Gugnani
Re: Data is not syncing up when we add one more Node(DR) to existing 3 node cluster
HI Anil,
Please follow the below link.
https://thelastpickle.com/blog/2019/02/26/data-center-switch.html
Did you ran the command nodetool rebuild old_dc_name to stream the old
historical data to new data center.
Step 9 of the above article.
On Thu, 12 Dec 2019 at 09:39, Anil Kumar Ganipineni <
akganipin...@adaequare.com> wrote:
> Hi All,
>
>
>
> We have 3 node cluster on datacentre DC1 and below is our key space
> declaration. The current data size on the cluster is ~10GB. When we add a
> new node on datacentre DC2, the new node is not syncing up with the data,
> but it is showing UN when I run the *nodetool status*.
>
>
>
> *CREATE* KEYSPACE *production* *WITH* REPLICATION = { 'class' :
> 'org.apache.cassandra.locator.NetworkTopologyStrategy', 'DC1': '3', 'DC2':
> '1' } *AND* DURABLE_WRITES = *true*;
>
>
>
>
>
> Please provide suggestions to make the new node on DC2 to sync up with
> existing cluster. This is required as the DC2 is our DR in a different
> region other than existing cluster.
>
>
>
>
>
> *Regards,*
>
> *Anil Ganipineni*
>
>
>
> *P** Please consider environment before printing this page.*
>
>
>
--
Raman Gugnani
Data is not syncing up when we add one more Node(DR) to existing 3 node cluster
Hi All,
We have 3 node cluster on datacentre DC1 and below is our key space
declaration. The current data size on the cluster is ~10GB. When we add a new
node on datacentre DC2, the new node is not syncing up with the data, but it is
showing UN when I run the nodetool status.
CREATE KEYSPACE production WITH REPLICATION = { 'class' :
'org.apache.cassandra.locator.NetworkTopologyStrategy', 'DC1': '3', 'DC2': '1'
} AND DURABLE_WRITES = true;
Please provide suggestions to make the new node on DC2 to sync up with existing
cluster. This is required as the DC2 is our DR in a different region other than
existing cluster.
Regards,
Anil Ganipineni
P Please consider environment before printing this page.
