Add nodes change

[wanshijie <ha...@139.com>]

Hello All,

We are going add 2 new nodes to our production server, there are 2 questions would like to have some advices?

1. In current production env, the cassandra version is 3.0.4, is it ok if we use 3.0.15 for the new node?
2. Current RF is 1, we would like change to 2, how does this change affect our production data, do we need to do any data migration? 

Thanks a lot
Shijie

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org

Re: [EXTERNAL] Add nodes change

[Jeff Jirsa <jj...@gmail.com>]

> On Dec 28, 2017, at 11:09 AM, Durity, Sean R <SE...@homedepot.com> wrote:
> 
> --> See inline
> 
> Hello All,
> 
> We are going add 2 new nodes to our production server, there are 2 questions would like to have some advices?
> 
> 1. In current production env, the cassandra version is 3.0.4, is it ok if we use 3.0.15 for the new node?
> 
> --> I would not do this. Streaming between versions usually doesn't work. Either upgrade the existing node before adding new ones OR do the upgrade after adding 3.0.4 nodes.


Especially across 3.0.14, we changed the internode messaging protocol. You’ll want to upgrade first and add new nodes second


> 
> 2. Current RF is 1, we would like change to 2, how does this change affect our production data, do we need to do any data migration?
> 
> --> Once you make the RF change, you will need to run repair on all nodes to have the existing data moved to the proper replicas. (New writes will be fine.) Until that is complete, query results may not be "correct." Depending on how critical the data and application are, it might be better to schedule an outage until the repairs are complete.

Or change the application to read at consistency level ALL until the repair is done


> 
> Thanks a lot
> Shijie
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
> 
> 
> ________________________________
> 
> The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org

RE: [EXTERNAL] Add nodes change

["Durity, Sean R" <SE...@homedepot.com>]

--> See inline

Hello All,

We are going add 2 new nodes to our production server, there are 2 questions would like to have some advices?

1. In current production env, the cassandra version is 3.0.4, is it ok if we use 3.0.15 for the new node?

--> I would not do this. Streaming between versions usually doesn't work. Either upgrade the existing node before adding new ones OR do the upgrade after adding 3.0.4 nodes.

2. Current RF is 1, we would like change to 2, how does this change affect our production data, do we need to do any data migration?

--> Once you make the RF change, you will need to run repair on all nodes to have the existing data moved to the proper replicas. (New writes will be fine.) Until that is complete, query results may not be "correct." Depending on how critical the data and application are, it might be better to schedule an outage until the repairs are complete.

Thanks a lot
Shijie

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org


________________________________

The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org