Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-30 Thread kurt greaves
On 30 January 2017 at 04:43, Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in> wrote:

> But how I will tell rebuild command source DC if I have more than 2 Dc?



You will need to rebuild the new DC from at least one DC for every keyspace
present on the new DC and the old DC's.
For example, if you have 2 DC's A, B, and add a new DC "C", with keyspace
"X" replicated to A and C, keyspace "Y" replicated to B and C, you will
need to rebuild the nodes from "C" from both DC's A and B, otherwise they
will not stream a full set of data for both keyspaces.

If all your keyspaces are replicated to all DC's, you only need to rebuild
from one other DC (which one doesn't *really* matter).

Note that if you rebuild multiple times on a node you will end up with
duplicate data. This isn't an issue, compactions will clean it up over
time. Usually if a rebuild fails for any reason you should wipe the data
directory to ensure you don't end up with 2 copies of a lot of the data.


Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-30 Thread Bhuvan Rawal
Hi Abhishek,

nodetool status output can be misleading at times.
In order to ensure data is in sync, schedule a repair for the imapcted
keyspaces.

Regards,

On Mon, Jan 30, 2017 at 10:13 AM, Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in> wrote:

> But how I will tell rebuild command source DC if I have more than 2 Dc?
>
>
>
> @dinking, yes I run the command, and it did some strange thing now:
>
>
>
> Datacenter: DRPOCcluster
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.29.XX.XXX  140.16 GB  256  ?   
> badf985b-37da-4735-b468-8d3a058d4b60
> 01
>
> UN  172.29. XX.XXX  82.04 GB   256  ?
> 317061b2-c19f-44ba-a776-bcd91c70bbdd  03
>
> UN  172.29. XX.XXX  85.29 GB   256  ?
> 9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
>
> Datacenter: dc_india
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.26. XX.XXX   79.09 GB   256  ?
> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>
> UN  172.26. XX.XXX   79.39 GB   256  ?
> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>
>
>
>
>
>
>
> In source DC (dc_india) we have near about 79 GB data. But in new DC each
> node has more than 79 GB data and Seed IP have near about 2 times data.
> Below is replication:
>
> Data Key Space:
>
> alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy',
> 'DRPOCcluster': '3','dc_india':'2'}  AND durable_writes = true;
>
> alter KEYSPACE adlog WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'2'}  AND
> durable_writes = true;
>
>
>
> New DC('DRPOCcluster') system Key Space:
>
>
>
> alter KEYSPACE system_distributed WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND
> durable_writes = true;
>
> alter KEYSPACE system_auth WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND
> durable_writes = true;
>
> alter KEYSPACE system_traces WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND
> durable_writes = true;
>
> alter KEYSPACE "OpsCenter" WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND
> durable_writes = true;
>
>
>
> Old  DC(‘dc_india’) system Key Space:
>
>
>
> alter KEYSPACE system_distributed WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND
> durable_writes = true;
>
> alter KEYSPACE system_auth WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND
> durable_writes = true;
>
> alter KEYSPACE system_traces WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND
> durable_writes = true;
>
> alter KEYSPACE "OpsCenter" WITH replication = {'class':
> 'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND
> durable_writes = true;
>
>
>
> why this happening? I did soething wrong?
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* kurt greaves [mailto:k...@instaclustr.com]
> *Sent:* Saturday, January 28, 2017 3:27 AM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
> new Cluster
>
>
>
> What Dikang said, in your original email you are passing -dc to rebuild.
> This is incorrect. Simply run nodetool rebuild  from each of the
> nodes in the new dc.
>
>
>
> On 28 Jan 2017 07:50, "Dikang Gu" <dikan...@gmail.com> wrote:
>
> Have you run 'nodetool rebuild dc_india' on the new nodes?
>
>
>
> On Tue, Jan 24, 2017 at 7:51 AM, Benjamin Roth <benjamin.r...@jaumo.com>
> wrote:
>
> Have you also altered RF of system_distributed as stated in the tutorial?
>
>
>
> 2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari <Abhishek.Maheshwari@
> timesinternet.in>:
>
> My Mistake,
>
>
>
> Both clusters are up and r

RE: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-29 Thread Abhishek Kumar Maheshwari
But how I will tell rebuild command source DC if I have more than 2 Dc?

@dinking, yes I run the command, and it did some strange thing now:

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.XX.XXX  140.16 GB  256  ?   
badf985b-37da-4735-b468-8d3a058d4b60  01
UN  172.29. XX.XXX  82.04 GB   256  ?   
317061b2-c19f-44ba-a776-bcd91c70bbdd  03
UN  172.29. XX.XXX  85.29 GB   256  ?   
9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.26. XX.XXX   79.09 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
UN  172.26. XX.XXX   79.39 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2



In source DC (dc_india) we have near about 79 GB data. But in new DC each node 
has more than 79 GB data and Seed IP have near about 2 times data. Below is 
replication:
Data Key Space:
alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy', 
'DRPOCcluster': '3','dc_india':'2'}  AND durable_writes = true;
alter KEYSPACE adlog WITH replication = {'class': 'NetworkTopologyStrategy', 
'DRPOCcluster': '3','dc_india':'2'}  AND durable_writes = true;

New DC('DRPOCcluster') system Key Space:

alter KEYSPACE system_distributed WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND 
durable_writes = true;
alter KEYSPACE system_auth WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND 
durable_writes = true;
alter KEYSPACE system_traces WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND 
durable_writes = true;
alter KEYSPACE "OpsCenter" WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '3','dc_india':'0'}  AND 
durable_writes = true;

Old  DC(‘dc_india’) system Key Space:

alter KEYSPACE system_distributed WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND 
durable_writes = true;
alter KEYSPACE system_auth WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND 
durable_writes = true;
alter KEYSPACE system_traces WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND 
durable_writes = true;
alter KEYSPACE "OpsCenter" WITH replication = {'class': 
'NetworkTopologyStrategy', 'DRPOCcluster': '0','dc_india':'2'}  AND 
durable_writes = true;

why this happening? I did soething wrong?

Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591 (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.

From: kurt greaves [mailto:k...@instaclustr.com]
Sent: Saturday, January 28, 2017 3:27 AM
To: user@cassandra.apache.org
Subject: Re: [Multi DC] Old Data Not syncing from Existing cluster to new 
Cluster

What Dikang said, in your original email you are passing -dc to rebuild. This 
is incorrect. Simply run nodetool rebuild  from each of the nodes in 
the new dc.

On 28 Jan 2017 07:50, "Dikang Gu" 
<dikan...@gmail.com<mailto:dikan...@gmail.com>> wrote:
Have you run 'nodetool rebuild dc_india' on the new nodes?

On Tue, Jan 24, 2017 at 7:51 AM, Benjamin Roth 
<benjamin.r...@jaumo.com<mailto:benjamin.r...@jaumo.com>> wrote:
Have you also altered RF of system_distributed as stated in the tutorial?

2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari 
<abhishek.maheshw...@timesinternet.in<mailto:abhishek.maheshw...@timesinternet.in>>:
My Mistake,

Both clusters are up and running.

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.XX.XX  1.65 GB   256  ?   
badf985b-37da-4735-b468-8d3a058d4b60  01
UN  172.29.XX.XX  1.64 GB   256  ?   
317061b2-c19f-44ba-a776-bcd91c70bbdd  03
UN  172.29.XX.XX  1.64 GB   256  ?   
9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.26.XX.XX   79.90 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
UN  172.26.XX.XX   80.21 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2

Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591<tel:+91%2099

Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-27 Thread kurt greaves
What Dikang said, in your original email you are passing -dc to rebuild.
This is incorrect. Simply run nodetool rebuild  from each of the
nodes in the new dc.

On 28 Jan 2017 07:50, "Dikang Gu" <dikan...@gmail.com> wrote:

> Have you run 'nodetool rebuild dc_india' on the new nodes?
>
> On Tue, Jan 24, 2017 at 7:51 AM, Benjamin Roth <benjamin.r...@jaumo.com>
> wrote:
>
>> Have you also altered RF of system_distributed as stated in the tutorial?
>>
>> 2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari <
>> abhishek.maheshw...@timesinternet.in>:
>>
>>> My Mistake,
>>>
>>>
>>>
>>> Both clusters are up and running.
>>>
>>>
>>>
>>> Datacenter: DRPOCcluster
>>>
>>> 
>>>
>>> Status=Up/Down
>>>
>>> |/ State=Normal/Leaving/Joining/Moving
>>>
>>> --  AddressLoad   Tokens   OwnsHost
>>> ID   Rack
>>>
>>> UN  172.29.XX.XX  1.65 GB   256  ?
>>> badf985b-37da-4735-b468-8d3a058d4b60  01
>>>
>>> UN  172.29.XX.XX  1.64 GB   256  ?
>>> 317061b2-c19f-44ba-a776-bcd91c70bbdd  03
>>>
>>> UN  172.29.XX.XX  1.64 GB   256  ?
>>> 9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
>>>
>>> Datacenter: dc_india
>>>
>>> 
>>>
>>> Status=Up/Down
>>>
>>> |/ State=Normal/Leaving/Joining/Moving
>>>
>>> --  AddressLoad   Tokens   OwnsHost
>>> ID   Rack
>>>
>>> UN  172.26.XX.XX   79.90 GB   256  ?
>>> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>>>
>>> UN  172.26.XX.XX   80.21 GB   256  ?
>>> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>>>
>>>
>>>
>>> *Thanks & Regards,*
>>> *Abhishek Kumar Maheshwari*
>>> *+91- 805591 <+91%208%2005591> (Mobile)*
>>>
>>> Times Internet Ltd. | A Times of India Group Company
>>>
>>> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>>>
>>> *P** Please do not print this email unless it is absolutely necessary.
>>> Spread environmental awareness.*
>>>
>>>
>>>
>>> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
>>> *Sent:* Tuesday, January 24, 2017 9:11 PM
>>> *To:* user@cassandra.apache.org
>>> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
>>> new Cluster
>>>
>>>
>>>
>>> I am not an expert in bootstrapping new DCs but shouldn't the OLD nodes
>>> appear as UP to be used as a streaming source in rebuild?
>>>
>>>
>>>
>>> 2017-01-24 16:32 GMT+01:00 Abhishek Kumar Maheshwari <
>>> abhishek.maheshw...@timesinternet.in>:
>>>
>>> Yes, I take all steps. While I am inserting new data is replicating on
>>> both DC. But only old data is not replication in new cluster.
>>>
>>>
>>>
>>> *Thanks & Regards,*
>>> *Abhishek Kumar Maheshwari*
>>> *+91- 805591 <+91%208%2005591> (Mobile)*
>>>
>>> Times Internet Ltd. | A Times of India Group Company
>>>
>>> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>>>
>>> *P** Please do not print this email unless it is absolutely necessary.
>>> Spread environmental awareness.*
>>>
>>>
>>>
>>> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
>>> *Sent:* Tuesday, January 24, 2017 8:55 PM
>>> *To:* user@cassandra.apache.org
>>> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
>>> new Cluster
>>>
>>>
>>>
>>> There is much more to it than just changing the RF in the keyspace!
>>>
>>>
>>>
>>> See here: https://docs.datastax.com/en/cassandra/3.0/cassandra/o
>>> perations/opsAddDCToCluster.html
>>>
>>>
>>>
>>> 2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari <
>>> abhishek.maheshw...@timesinternet.in>:
>>>
>>> Hi All,
>>>
>>>
>>>
>>> I have Cassandra stack with 2 Dc
>>>
>>>
>>>
>>> Datacenter: DRPOCcluster
>>>
>>> 
>>>
>>> Status=Up/Down
>>>
>>> |/ State=Nor

Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-27 Thread Dikang Gu
Have you run 'nodetool rebuild dc_india' on the new nodes?

On Tue, Jan 24, 2017 at 7:51 AM, Benjamin Roth <benjamin.r...@jaumo.com>
wrote:

> Have you also altered RF of system_distributed as stated in the tutorial?
>
> 2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari <Abhishek.Maheshwari@
> timesinternet.in>:
>
>> My Mistake,
>>
>>
>>
>> Both clusters are up and running.
>>
>>
>>
>> Datacenter: DRPOCcluster
>>
>> 
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   OwnsHost
>> ID   Rack
>>
>> UN  172.29.XX.XX  1.65 GB   256  ?
>> badf985b-37da-4735-b468-8d3a058d4b60  01
>>
>> UN  172.29.XX.XX  1.64 GB   256  ?
>> 317061b2-c19f-44ba-a776-bcd91c70bbdd  03
>>
>> UN  172.29.XX.XX  1.64 GB   256  ?
>> 9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
>>
>> Datacenter: dc_india
>>
>> 
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   OwnsHost
>> ID   Rack
>>
>> UN  172.26.XX.XX   79.90 GB   256  ?
>> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>>
>> UN  172.26.XX.XX   80.21 GB   256  ?
>> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>>
>>
>>
>> *Thanks & Regards,*
>> *Abhishek Kumar Maheshwari*
>> *+91- 805591 <+91%208%2005591> (Mobile)*
>>
>> Times Internet Ltd. | A Times of India Group Company
>>
>> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>>
>> *P** Please do not print this email unless it is absolutely necessary.
>> Spread environmental awareness.*
>>
>>
>>
>> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
>> *Sent:* Tuesday, January 24, 2017 9:11 PM
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
>> new Cluster
>>
>>
>>
>> I am not an expert in bootstrapping new DCs but shouldn't the OLD nodes
>> appear as UP to be used as a streaming source in rebuild?
>>
>>
>>
>> 2017-01-24 16:32 GMT+01:00 Abhishek Kumar Maheshwari <
>> abhishek.maheshw...@timesinternet.in>:
>>
>> Yes, I take all steps. While I am inserting new data is replicating on
>> both DC. But only old data is not replication in new cluster.
>>
>>
>>
>> *Thanks & Regards,*
>> *Abhishek Kumar Maheshwari*
>> *+91- 805591 <+91%208%2005591> (Mobile)*
>>
>> Times Internet Ltd. | A Times of India Group Company
>>
>> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>>
>> *P** Please do not print this email unless it is absolutely necessary.
>> Spread environmental awareness.*
>>
>>
>>
>> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
>> *Sent:* Tuesday, January 24, 2017 8:55 PM
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
>> new Cluster
>>
>>
>>
>> There is much more to it than just changing the RF in the keyspace!
>>
>>
>>
>> See here: https://docs.datastax.com/en/cassandra/3.0/cassandra/
>> operations/opsAddDCToCluster.html
>>
>>
>>
>> 2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari <
>> abhishek.maheshw...@timesinternet.in>:
>>
>> Hi All,
>>
>>
>>
>> I have Cassandra stack with 2 Dc
>>
>>
>>
>> Datacenter: DRPOCcluster
>>
>> 
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   OwnsHost
>> ID   Rack
>>
>> UN  172.29.xx.xxx  256  MB   256  ?
>> b6b8cbb9-1fed-471f-aea9-6a657e7ac80a  01
>>
>> UN  172.29.xx.xxx  240 MB   256  ?
>> 604abbf5-8639-4104-8f60-fd6573fb2e17  03
>>
>> UN  172.29. xx.xxx  240 MB   256  ?
>> 32fa79ee-93c6-4e5b-a910-f27a1e9d66c1  02
>>
>> Datacenter: dc_india
>>
>> 
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   OwnsHost
>> ID   Rack
>>
>> DN  172.2

Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Benjamin Roth
Have you also altered RF of system_distributed as stated in the tutorial?

2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in>:

> My Mistake,
>
>
>
> Both clusters are up and running.
>
>
>
> Datacenter: DRPOCcluster
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.29.XX.XX  1.65 GB   256  ?   
> badf985b-37da-4735-b468-8d3a058d4b60
> 01
>
> UN  172.29.XX.XX  1.64 GB   256  ?   
> 317061b2-c19f-44ba-a776-bcd91c70bbdd
> 03
>
> UN  172.29.XX.XX  1.64 GB   256  ?   
> 9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c
> 02
>
> Datacenter: dc_india
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.26.XX.XX   79.90 GB   256  ?   
> 3e8133ed-98b5-418d-96b5-690a1450cd30
> RACK1
>
> UN  172.26.XX.XX   80.21 GB   256  ?   
> 7d3f5b25-88f9-4be7-b0f5-746619153543
> RACK2
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 <+91%208%2005591> (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
> *Sent:* Tuesday, January 24, 2017 9:11 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
> new Cluster
>
>
>
> I am not an expert in bootstrapping new DCs but shouldn't the OLD nodes
> appear as UP to be used as a streaming source in rebuild?
>
>
>
> 2017-01-24 16:32 GMT+01:00 Abhishek Kumar Maheshwari <Abhishek.Maheshwari@
> timesinternet.in>:
>
> Yes, I take all steps. While I am inserting new data is replicating on
> both DC. But only old data is not replication in new cluster.
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 <+91%208%2005591> (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
> *Sent:* Tuesday, January 24, 2017 8:55 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
> new Cluster
>
>
>
> There is much more to it than just changing the RF in the keyspace!
>
>
>
> See here: https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/
> opsAddDCToCluster.html
>
>
>
> 2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari <Abhishek.Maheshwari@
> timesinternet.in>:
>
> Hi All,
>
>
>
> I have Cassandra stack with 2 Dc
>
>
>
> Datacenter: DRPOCcluster
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.29.xx.xxx  256  MB   256  ?   
> b6b8cbb9-1fed-471f-aea9-6a657e7ac80a
> 01
>
> UN  172.29.xx.xxx  240 MB   256  ?   
> 604abbf5-8639-4104-8f60-fd6573fb2e17
> 03
>
> UN  172.29. xx.xxx  240 MB   256  ?   
> 32fa79ee-93c6-4e5b-a910-f27a1e9d66c1
> 02
>
> Datacenter: dc_india
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> DN  172.26. .xx.xxx  78.97 GB   256  ?
> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>
> DN  172.26. .xx.xxx  79.18 GB   256  ?
> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>
>
>
> dc_india is old Dc which contains all data.
>
> I update keyspace as per below:
>
>
>
> alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy',
> 'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;
>
>
>
> but old data is not updating in DRPOCcluster(which is new). Also, while
> running nodetool rebuild getting below exception:
>
> Cammand: ./nodetool rebuild -dc dc_india
>
>
>
> Exception : nodetool: U

RE: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Abhishek Kumar Maheshwari
My Mistake,

Both clusters are up and running.

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.XX.XX  1.65 GB   256  ?   
badf985b-37da-4735-b468-8d3a058d4b60  01
UN  172.29.XX.XX  1.64 GB   256  ?   
317061b2-c19f-44ba-a776-bcd91c70bbdd  03
UN  172.29.XX.XX  1.64 GB   256  ?   
9bf0d1dc-6826-4f3b-9c56-cec0c9ce3b6c  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.26.XX.XX   79.90 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
UN  172.26.XX.XX   80.21 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2

Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591 (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.

From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: Tuesday, January 24, 2017 9:11 PM
To: user@cassandra.apache.org
Subject: Re: [Multi DC] Old Data Not syncing from Existing cluster to new 
Cluster

I am not an expert in bootstrapping new DCs but shouldn't the OLD nodes appear 
as UP to be used as a streaming source in rebuild?

2017-01-24 16:32 GMT+01:00 Abhishek Kumar Maheshwari 
<abhishek.maheshw...@timesinternet.in<mailto:abhishek.maheshw...@timesinternet.in>>:
Yes, I take all steps. While I am inserting new data is replicating on both DC. 
But only old data is not replication in new cluster.

Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591<tel:+91%208%2005591> (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.

From: Benjamin Roth 
[mailto:benjamin.r...@jaumo.com<mailto:benjamin.r...@jaumo.com>]
Sent: Tuesday, January 24, 2017 8:55 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: [Multi DC] Old Data Not syncing from Existing cluster to new 
Cluster

There is much more to it than just changing the RF in the keyspace!

See here: 
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html

2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari 
<abhishek.maheshw...@timesinternet.in<mailto:abhishek.maheshw...@timesinternet.in>>:
Hi All,

I have Cassandra stack with 2 Dc

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.xx.xxx  256  MB   256  ?   
b6b8cbb9-1fed-471f-aea9-6a657e7ac80a  01
UN  172.29.xx.xxx  240 MB   256  ?   
604abbf5-8639-4104-8f60-fd6573fb2e17  03
UN  172.29. xx.xxx  240 MB   256  ?   
32fa79ee-93c6-4e5b-a910-f27a1e9d66c1  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
DN  172.26. .xx.xxx  78.97 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
DN  172.26. .xx.xxx  79.18 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2

dc_india is old Dc which contains all data.
I update keyspace as per below:

alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy', 
'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;

but old data is not updating in DRPOCcluster(which is new). Also, while running 
nodetool rebuild getting below exception:
Cammand: ./nodetool rebuild -dc dc_india

Exception : nodetool: Unable to find sufficient sources for streaming range 
(-875697427424852,-8755484427030035332] in keyspace system_distributed

Cassandra version : 3.0.9


Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591<tel:+91%208%2005591> (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.




--
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com<http://www.jaumo.com>
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6<tel:07161%203048806> · Fax +49 7161 
304880-1<tel:07161%203048801>
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer



--
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com<http://www.jaumo.com>
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer


Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Benjamin Roth
I am not an expert in bootstrapping new DCs but shouldn't the OLD nodes
appear as UP to be used as a streaming source in rebuild?

2017-01-24 16:32 GMT+01:00 Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in>:

> Yes, I take all steps. While I am inserting new data is replicating on
> both DC. But only old data is not replication in new cluster.
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 <+91%208%2005591> (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
> *Sent:* Tuesday, January 24, 2017 8:55 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: [Multi DC] Old Data Not syncing from Existing cluster to
> new Cluster
>
>
>
> There is much more to it than just changing the RF in the keyspace!
>
>
>
> See here: https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/
> opsAddDCToCluster.html
>
>
>
> 2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari <Abhishek.Maheshwari@
> timesinternet.in>:
>
> Hi All,
>
>
>
> I have Cassandra stack with 2 Dc
>
>
>
> Datacenter: DRPOCcluster
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.29.xx.xxx  256  MB   256  ?   
> b6b8cbb9-1fed-471f-aea9-6a657e7ac80a
> 01
>
> UN  172.29.xx.xxx  240 MB   256  ?   
> 604abbf5-8639-4104-8f60-fd6573fb2e17
> 03
>
> UN  172.29. xx.xxx  240 MB   256  ?   
> 32fa79ee-93c6-4e5b-a910-f27a1e9d66c1
> 02
>
> Datacenter: dc_india
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> DN  172.26. .xx.xxx  78.97 GB   256  ?
> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>
> DN  172.26. .xx.xxx  79.18 GB   256  ?
> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>
>
>
> dc_india is old Dc which contains all data.
>
> I update keyspace as per below:
>
>
>
> alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy',
> 'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;
>
>
>
> but old data is not updating in DRPOCcluster(which is new). Also, while
> running nodetool rebuild getting below exception:
>
> Cammand: ./nodetool rebuild -dc dc_india
>
>
>
> Exception : nodetool: Unable to find sufficient sources for streaming
> range (-875697427424852,-8755484427030035332] in keyspace
> system_distributed
>
>
>
> Cassandra version : 3.0.9
>
>
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 <+91%208%2005591> (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
>
>
>
>
> --
>
> Benjamin Roth
> Prokurist
>
> Jaumo GmbH · www.jaumo.com
> Wehrstraße 46 · 73035 Göppingen · Germany
> Phone +49 7161 304880-6 <07161%203048806> · Fax +49 7161 304880-1
> <07161%203048801>
> AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
>



-- 
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer


RE: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Abhishek Kumar Maheshwari
Yes, I take all steps. While I am inserting new data is replicating on both DC. 
But only old data is not replication in new cluster.

Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591 (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.

From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: Tuesday, January 24, 2017 8:55 PM
To: user@cassandra.apache.org
Subject: Re: [Multi DC] Old Data Not syncing from Existing cluster to new 
Cluster

There is much more to it than just changing the RF in the keyspace!

See here: 
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html

2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari 
<abhishek.maheshw...@timesinternet.in<mailto:abhishek.maheshw...@timesinternet.in>>:
Hi All,

I have Cassandra stack with 2 Dc

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.xx.xxx  256  MB   256  ?   
b6b8cbb9-1fed-471f-aea9-6a657e7ac80a  01
UN  172.29.xx.xxx  240 MB   256  ?   
604abbf5-8639-4104-8f60-fd6573fb2e17  03
UN  172.29. xx.xxx  240 MB   256  ?   
32fa79ee-93c6-4e5b-a910-f27a1e9d66c1  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
DN  172.26. .xx.xxx  78.97 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
DN  172.26. .xx.xxx  79.18 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2

dc_india is old Dc which contains all data.
I update keyspace as per below:

alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy', 
'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;

but old data is not updating in DRPOCcluster(which is new). Also, while running 
nodetool rebuild getting below exception:
Cammand: ./nodetool rebuild -dc dc_india

Exception : nodetool: Unable to find sufficient sources for streaming range 
(-875697427424852,-8755484427030035332] in keyspace system_distributed

Cassandra version : 3.0.9


Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591<tel:+91%208%2005591> (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.




--
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com<http://www.jaumo.com>
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer


Re: [Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Benjamin Roth
There is much more to it than just changing the RF in the keyspace!

See here:
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddDCToCluster.html

2017-01-24 16:18 GMT+01:00 Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in>:

> Hi All,
>
>
>
> I have Cassandra stack with 2 Dc
>
>
>
> Datacenter: DRPOCcluster
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> UN  172.29.xx.xxx  256  MB   256  ?   
> b6b8cbb9-1fed-471f-aea9-6a657e7ac80a
> 01
>
> UN  172.29.xx.xxx  240 MB   256  ?   
> 604abbf5-8639-4104-8f60-fd6573fb2e17
> 03
>
> UN  172.29. xx.xxx  240 MB   256  ?   
> 32fa79ee-93c6-4e5b-a910-f27a1e9d66c1
> 02
>
> Datacenter: dc_india
>
> 
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   OwnsHost
> ID   Rack
>
> DN  172.26. .xx.xxx  78.97 GB   256  ?
> 3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
>
> DN  172.26. .xx.xxx  79.18 GB   256  ?
> 7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2
>
>
>
> dc_india is old Dc which contains all data.
>
> I update keyspace as per below:
>
>
>
> alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy',
> 'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;
>
>
>
> but old data is not updating in DRPOCcluster(which is new). Also, while
> running nodetool rebuild getting below exception:
>
> Cammand: ./nodetool rebuild -dc dc_india
>
>
>
> Exception : nodetool: Unable to find sufficient sources for streaming
> range (-875697427424852,-8755484427030035332] in keyspace
> system_distributed
>
>
>
> Cassandra version : 3.0.9
>
>
>
>
>
> *Thanks & Regards,*
> *Abhishek Kumar Maheshwari*
> *+91- 805591 <+91%208%2005591> (Mobile)*
>
> Times Internet Ltd. | A Times of India Group Company
>
> FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>



-- 
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer


[Multi DC] Old Data Not syncing from Existing cluster to new Cluster

2017-01-24 Thread Abhishek Kumar Maheshwari
Hi All,

I have Cassandra stack with 2 Dc

Datacenter: DRPOCcluster

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
UN  172.29.xx.xxx  256  MB   256  ?   
b6b8cbb9-1fed-471f-aea9-6a657e7ac80a  01
UN  172.29.xx.xxx  240 MB   256  ?   
604abbf5-8639-4104-8f60-fd6573fb2e17  03
UN  172.29. xx.xxx  240 MB   256  ?   
32fa79ee-93c6-4e5b-a910-f27a1e9d66c1  02
Datacenter: dc_india

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  AddressLoad   Tokens   OwnsHost ID  
 Rack
DN  172.26. .xx.xxx  78.97 GB   256  ?   
3e8133ed-98b5-418d-96b5-690a1450cd30  RACK1
DN  172.26. .xx.xxx  79.18 GB   256  ?   
7d3f5b25-88f9-4be7-b0f5-746619153543  RACK2

dc_india is old Dc which contains all data.
I update keyspace as per below:

alter KEYSPACE wls WITH replication = {'class': 'NetworkTopologyStrategy', 
'DRPOCcluster': '2','dc_india':'2'}  AND durable_writes = true;

but old data is not updating in DRPOCcluster(which is new). Also, while running 
nodetool rebuild getting below exception:
Cammand: ./nodetool rebuild -dc dc_india

Exception : nodetool: Unable to find sufficient sources for streaming range 
(-875697427424852,-8755484427030035332] in keyspace system_distributed

Cassandra version : 3.0.9


Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591 (Mobile)
Times Internet Ltd. | A Times of India Group Company
FC - 6, Sector 16A, Film City,  Noida,  U.P. 201301 | INDIA
P Please do not print this email unless it is absolutely necessary. Spread 
environmental awareness.