From user-return-60067-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Tue Feb 27 15:18:49 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 49B63180651 for ; Tue, 27 Feb 2018 15:18:49 +0100 (CET) Received: (qmail 26615 invoked by uid 500); 27 Feb 2018 14:18:47 -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 26601 invoked by uid 99); 27 Feb 2018 14:18:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Feb 2018 14:18:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E4C981801AF for ; Tue, 27 Feb 2018 14:18:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FJuZ17ZmRv4U for ; Tue, 27 Feb 2018 14:18:46 +0000 (UTC) Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 37F435F5AF for ; Tue, 27 Feb 2018 14:18:45 +0000 (UTC) Received: by mail-it0-f41.google.com with SMTP id v194so15476745itb.0 for ; Tue, 27 Feb 2018 06:18:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=WJya8y0sqKmKQEqeIzbDqcTeoA0Shi31jLovxOFJlsg=; b=XHopukQkV7VQin1Dwwwufkpnoi3X3w6EwhP4gTLRiE/PHnYMQbdB43gJPe3jeTWF/e cQStrSlHb7nHLINpoP4z7ONeQRvjVXiniHLN4ez17HmZ9rs2NSHr4hhZ9yUPZdgAjDQP 41cAmBsoR79A2ifiBiVEN4hEifEdpSrzm5lOOjiCV2g3e4d2WrGDOYHDQpWICr2mxSN7 /fCVtmfyTqUI8DtE1zwF4POn9gpNj3vU08rmk1J+YFzBowbNfs8BGZeg/+KXcj4yhfTV xF0s+sw/kj/6oVALzbS35N7vYu12NgEowUpc2VchQ/F+kvhUm7+scxZElzVx6WQ8o7fx Wc4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WJya8y0sqKmKQEqeIzbDqcTeoA0Shi31jLovxOFJlsg=; b=Ock/fVthpGhPHUffpgkA41OfU7Qkb+DesRAEzcL4kYS/aHwCuHFjuAGb3xRljlHdBn q6Em1xauxthASEGz0LVEZQXMOqcWPp7EA8Rl8LCfXfjWE80I7Khul84BfKWR0pVyN77B PZ6PqZ6DKR4HIMU+4To7fsoLlRHZMx79yNXUfDzmpGCVp8H2dc8BNLvsF3tKjvIXHiRa Ya9eKKbmTeDO5WdnD+BTE6E3oUHcTxZUh7YIa7wLWfZGnKlNyZzD2xlYABqvIFpbaow9 c4rNHGxnd7pjFC0diC4R3UwfAND/HDfRhdU1Z4z0XSlngth5kB1zamlsKsyzw+0Jong8 Er3A== X-Gm-Message-State: APf1xPBNjLabjnwInGMAR/q/NF3gth64oVMfOLU2b9O6zOSYB1z+jKMB N9uqoRm4tKUwTaJYSXxhbF9DHcw1WKfrV1kOVsw= X-Google-Smtp-Source: AG47ELsLwtjLOa9fmjdPBceJuZSfS3vLRkJ+irVdchks1CrvSAk42hbgd0gX0v6RKVXKR9WxNSJm7MIjS0ZhMOoT2Lg= X-Received: by 10.36.179.8 with SMTP id e8mr1631868itf.36.1519741117785; Tue, 27 Feb 2018 06:18:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.77.139 with HTTP; Tue, 27 Feb 2018 06:18:37 -0800 (PST) From: shalom sagges Date: Tue, 27 Feb 2018 16:18:37 +0200 Message-ID: Subject: Version Rollback To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary="f4030439e04c79f4db0566324d5f" --f4030439e04c79f4db0566324d5f Content-Type: text/plain; charset="UTF-8" Hi All, I'm planning to upgrade my C* cluster to version 3.x and was wondering what's the best way to perform a rollback if need be. If I used snapshot restoration, I would be facing data loss, depends when I took the snapshot (i.e. a rollback might be required after upgrading half the cluster for example). If I add another DC to the cluster with the old version, then I could point the apps to talk to that DC if anything bad happens, but building it is really time consuming and requires a lot of resources. Can anyone provide recommendations on this matter? Any ideas on how to make the upgrade foolproof, or at least "really really safe"? Thanks! --f4030439e04c79f4db0566324d5f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

I'm pla= nning to upgrade my C* cluster to version 3.x and was wondering what's = the best way to perform a rollback if need be.

If I used snap= shot restoration, I would be facing data loss, depends when I took the snap= shot (i.e. a rollback might be required after upgrading half the cluster fo= r example).

If I add another DC to the cluster with the old v= ersion, then I could point the apps to talk to that DC if anything bad happ= ens, but building it is really time consuming and requires a lot of resourc= es.

Can anyone provide recommendations on this matter? A= ny ideas on how to make the upgrade foolproof, or at least "really rea= lly safe"?

Thanks!



=
--f4030439e04c79f4db0566324d5f--