So,

If you are just moving data to another node, you can just start the new C*
node up without any replace_address parameters. Cassandra will treat it as
existing node with changed IP address (assuming all files within data are
moved).

Hannu


On 27 June 2017 at 20:43:18, Anuj Wadehra (anujw_2...@yahoo.co.in) wrote:

Hi Nitan,

I think it would be simpler to take one node down at a time and replace it
by bringing the new node up after linux upgrade, doing same cassandra
setup, using replace_address option and setting autobootstrap=false ( as
data is already there). No downtime as it would be a rolling upgrade. No
streaming as same tokens would work.

If you have latest C*, use replace_address_first_boot. If option not
available, use replace_address and make sure you remove it once new node is
up.

Try it and let us know if it works for you.

Thanks
Anuj



On Tue, Jun 27, 2017 at 4:56 AM, Nitan Kainth
<ni...@bamlabs.com> wrote:
Right, we are just upgrading Linux on AWS. C* will remain at same version.


On Jun 26, 2017, at 6:05 PM, Hannu Kröger <hkro...@gmail.com> wrote:

I understood he is updating linux, not C*

Hannu

On 27 June 2017 at 02:04:34, Jonathan Haddad (j...@jonhaddad.com) wrote:

It sounds like you're suggesting adding new nodes in to replace existing
ones.  You can't do that because it requires streaming between versions,
which isn't supported.

You need to take a node down, upgrade the C* version, then start it back
up.

Jon

On Mon, Jun 26, 2017 at 3:56 PM Nitan Kainth <ni...@bamlabs.com> wrote:

It's vnodes. We will add to replace new ip in yaml as well.

Thank you.

Sent from my iPhone

> On Jun 26, 2017, at 4:47 PM, Hannu Kröger <hkro...@gmail.com> wrote:
>
> Looks Ok. Step 1.5 would be to stop cassandra on existing node but apart
from that looks fine. Assuming you are using same configs and if you have
hard coded the token(s), you use the same.
>
> Hannu
>
>> On 26 Jun 2017, at 23.24, Nitan Kainth <ni...@sleepiqlabs.com> wrote:
>>
>> Hi,
>>
>> We are planning to update linux for C* nodes version 3.0. Anybody has
steps who did it recent past.
>>
>> Here are draft steps, we are thinking:
>> 1. Create new node. It might have a different IP address.
>> 2. Detach mounts from existing node
>> 3. Attach mounts to new Node
>> 4. Start C*

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

Reply via email to