Re: Linux version update on DSE

Good point. > On Jun 27, 2017, at 1:34 PM, Anuj Wadehra wrote: > > Also, if you restore exactly same data with different IP, you may need to > clear gossip state on the node. > > Anuj > > Sent from Yahoo Mail on Android >

Re: Linux version update on DSE

Also, if you restore exactly same data with different IP, you may need to clear gossip state on the node. Anuj Sent from Yahoo Mail on Android On Tue, Jun 27, 2017 at 11:56 PM, Anuj Wadehra wrote: Hi Nitan, I asked for adding autobootstrap false to avoid

Re: Linux version update on DSE

Thats right Hannu. We are planning to go with this approach instead of replace_address. > On Jun 27, 2017, at 12:48 PM, Hannu Kröger wrote: > > So, > > If you are just moving data to another node, you can just start the new C* > node up without any replace_address

Re: Linux version update on DSE

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

Re: Linux version update on DSE

Anuj, We did that in past, even if data was not removed, replace_node caused data streaming. So changing IP is simplest and safest option. > On Jun 27, 2017, at 12:43 PM, Anuj Wadehra wrote: > > replace_address_first_boot

Re: Linux version update on DSE

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

Re: Linux version update on DSE

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 wrote: > > I understood he is updating linux, not C* > > Hannu > On 27 June 2017 at 02:04:34, Jonathan Haddad (j...@jonhaddad.com >

Re: Linux version update on DSE

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

Re: Linux version update on DSE

Oops, I read that wrong, sorry. You want to upgrade the OS. Disregard my email. On Mon, Jun 26, 2017 at 4:04 PM Jonathan Haddad wrote: > It sounds like you're suggesting adding new nodes in to replace existing > ones. You can't do that because it requires streaming

Re: Linux version update on DSE

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

Re: Linux version update on DSE

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 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

Re: Linux version update on DSE

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 wrote: > > Hi, > > We are

Linux version update on DSE

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*