Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1F7F8200CB4 for ; Tue, 27 Jun 2017 19:43:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1DAF0160BDC; Tue, 27 Jun 2017 17:43:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 16A78160BD8 for ; Tue, 27 Jun 2017 19:43:29 +0200 (CEST) Received: (qmail 38304 invoked by uid 500); 27 Jun 2017 17:43:28 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 38290 invoked by uid 99); 27 Jun 2017 17:43:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 17:43:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id DBDBFC111F for ; Tue, 27 Jun 2017 17:43:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.4 X-Spam-Level: ** X-Spam-Status: No, score=2.4 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.in Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 5kSQ2rvxICom for ; Tue, 27 Jun 2017 17:43:25 +0000 (UTC) Received: from sonic318-21.consmr.mail.sg3.yahoo.com (sonic318-21.consmr.mail.sg3.yahoo.com [106.10.243.141]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 0153E60D53 for ; Tue, 27 Jun 2017 17:43:24 +0000 (UTC) X-YMail-OSG: Vi1pyOsVRDtKj1.x2JZALveVDFzSdW4pKQFy6WbaxSqGKco- Received: from sonic.gate.mail.ne1.yahoo.com by sonic318.consmr.mail.sg3.yahoo.com with HTTP; Tue, 27 Jun 2017 17:43:17 +0000 Date: Tue, 27 Jun 2017 17:43:15 +0000 (UTC) From: Anuj Wadehra Reply-To: "anujw_2003@yahoo.co.in" To: Nitan Kainth , =?UTF-8?Q?Hannu_Kr=C3=B6ger?= Cc: Jonathan Haddad , Nitan Kainth , "user@cassandra.apache.org" Message-ID: <1228534871.3203210.1498585395032@mail.yahoo.com> In-Reply-To: <92D688DD-ADF9-4128-AAC0-76C76E47C4A9@bamlabs.com> References: <0A95D90D-57BD-4910-8868-A7BAD5AE68C7@gmail.com> <14691470-1138-4665-B902-56C17AE1DA00@bamlabs.com> <92D688DD-ADF9-4128-AAC0-76C76E47C4A9@bamlabs.com> Subject: Re: Linux version update on DSE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3203209_1963795064.1498585395029" X-Mailer: WebService/1.1.9948 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/5.12.4; Android/6.0.1; MMB29M; htc_melsuhl; HTC; HTC One_M8 Eye; 4.64; 1776x1080;) archived-at: Tue, 27 Jun 2017 17:43:31 -0000 ------=_Part_3203209_1963795064.1498585395029 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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=3Dfalse ( as data = is already there). No downtime as it would be a rolling upgrade. No streami= ng as same tokens would work. If you have latest C*, use replace_address_first_boot. If option not availa= ble, 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. ThanksAnuj =20 =20 On Tue, Jun 27, 2017 at 4:56 AM, Nitan Kainth 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=C3=B6ger wrote: I understood he is updating linux, not C* Hannu On 27 June 2017 at 02:04:34, Jonathan Haddad (jon@jonhaddad.com) wrote: It sounds like you're suggesting adding new nodes in to replace existing on= es.=C2=A0 You can't do that because it requires streaming between versions,= which isn't supported.=C2=A0 You need to take a node down, upgrade the C* version, then start it back up= . =C2=A0 Jon On Mon, Jun 26, 2017 at 3:56 PM Nitan Kainth 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=C3=B6ger 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 h= ard coded the token(s), you use the same. > > Hannu > >> On 26 Jun 2017, at 23.24, Nitan Kainth wrote: >> >> Hi, >> >> We are planning to update linux for C* nodes version 3.0. Anybody has st= eps 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:=C2=A0user-unsubscribe@cassandra.apache.org For additional commands, e-mail:=C2=A0user-help@cassandra.apache.org =20 ------=_Part_3203209_1963795064.1498585395029 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Nitan,

I think it would be simpl= er 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 o= ption and setting autobootstrap=3Dfalse ( as data is already there). No dow= ntime as it would be a rolling upgrade. No streaming as same tokens would w= ork.

If you have latest C*, u= se 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 Ka= inth
<nitan@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, H= annu Kr=C3=B6ger <hkroger@gmail.com> wrote:

I understood he is updating linux= , not C*

Hannu

On 27 June 2017 at 02:04:34, Jonathan Haddad (jon@jo= nhaddad.com) wrote:

It sound= s like you're suggesting adding new nodes in to replace existing ones. = ; You can't do that because it requires streaming between versions, which i= sn't supported. 

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

Jon

On Mon, Jun 26, 2017 at 3:56 PM Nitan Kainth <nitan@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=C3=B6ger <hkroger@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 Kai= nth <nitan@sleepiqlabs.com> wrote:
>>
>&= gt; Hi,
>>
>> We are planning to update linux for C* n= odes 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 I= P address.
>> 2. Detach mou= nts from existing node
>> 3= . Attach mounts to new Node
>&= gt; 4. Start C*

-------------------------------------------------= --------------------
To unsubscri= be, e-mail: = user-unsubscribe@cassandra.apache.org=
For additional commands, e-m= ail: user-help@cassandra.apache.org

------=_Part_3203209_1963795064.1498585395029--