From user-return-62468-archive-asf-public=cust-asf.ponee.io@cassandra.apache.org Tue Oct 9 15:30:27 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 C1BC2180668 for ; Tue, 9 Oct 2018 15:30:26 +0200 (CEST) Received: (qmail 46400 invoked by uid 500); 9 Oct 2018 13:30:25 -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 46390 invoked by uid 99); 9 Oct 2018 13:30:24 -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, 09 Oct 2018 13:30:24 +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 6FE52180711 for ; Tue, 9 Oct 2018 13:30:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.888 X-Spam-Level: * X-Spam-Status: No, score=1.888 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_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] 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 QqAwwYieu8Ed for ; Tue, 9 Oct 2018 13:30:23 +0000 (UTC) Received: from mail-vs1-f54.google.com (mail-vs1-f54.google.com [209.85.217.54]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E563C5F2F0 for ; Tue, 9 Oct 2018 13:30:22 +0000 (UTC) Received: by mail-vs1-f54.google.com with SMTP id c205so1486894vsd.3 for ; Tue, 09 Oct 2018 06:30:22 -0700 (PDT) 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=VZ8hQXell+iov/KqqlBwie2UjWGH/4ah23eY3Wzgu14=; b=T69//8jfLafbKjO+SwbY7MSmcwCB37ZVEi5fDOIhaGILHoMK64Zk78uf0HkvW2WLw3 tSvHbHZYkstehvRXQoArogRL+hSxwUX+IgBzWUiB+67pWG1p+n2fEVvZvqumoj3rJ2O7 8jJJFngQR6XnkzAjzeubpWmcEMbZdFHRGfUdWkwDr8eFncC8cpGAK51ME8wgvzXz6P4B IcoAKJ5zmT+V0TVe/GBiQysBa6FPGGRZmc9UT7k4WS02ERd9U2NPC7wc/0T8ZYlK0/Ve CabDYjpajhK3CKBPKJSqqYAtc93uCJEKbnsPk73hgP0NA07xpDgG/1yqGprTTJZr81sm 9sgg== 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=VZ8hQXell+iov/KqqlBwie2UjWGH/4ah23eY3Wzgu14=; b=ImBRbHSN+YSTiX80AHPVBABmLId7y3vATrtu9h8QVY48o/rjpIwgkiWU0LxXEJEexh XprhbWe+aHWmif4zzYyWMAmNWvMJulfseBLVMCB3+F53Ip/V3LqqqLUPKCSnZDqWFmYv lw5u6Tp+jiOldoTyzLM70sF5WYOu/fiVe5I6EBQK9l/8c7ooOUaXOIYwgGZuJ4ZUbl9V 7n8q2R5rxUGneEuAGraI45rCmi1hTEXITyejcoZMATIkfps6aTnBynfy93bBM+Zy7//S nwV9dXaqKl/sWZai71ksAkriBKkpdre30dRojjrAsiFKHNQv6phIF4RH1s0orJ18Hebw 7Umw== X-Gm-Message-State: ABuFfoiEGEtt2oJiRBr5qNzNqhIvtaifkDoFetS2liFAzwHMNdl4YQ1H Sfgru4fEM4lYDMeSNSNAwo8SVqF+YiBmGcEdWtN6Cw== X-Google-Smtp-Source: ACcGV62X/bd9JIuHurRLnofk3Wtf0f/bBJxiDZQoQ/nkN7nODzgXQ0grN/j/eIkxLspGXxgugkw3uqGXwIwB57ajPJc= X-Received: by 2002:ab0:4e8b:: with SMTP id l11mr11401009uah.93.1539091821535; Tue, 09 Oct 2018 06:30:21 -0700 (PDT) MIME-Version: 1.0 From: Riccardo Ferrari Date: Tue, 9 Oct 2018 15:30:10 +0200 Message-ID: Subject: Upgraded to 3.0.17, stop here or move forward? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary="0000000000004ca6e80577cbbd0a" --0000000000004ca6e80577cbbd0a Content-Type: text/plain; charset="UTF-8" Hi list, We recently upgraded our small cluster to the latest 3.0.17. Everything was nice and smooth, however I am wondering if ti make sense to keep moving forward and upgarde to the latest 3.11.3? We really need something like the GROUP_BY and UFF/UDA seems limited wrt our use-case. Does it make sense? Any argument against? Is there any doc to prepare such upgrade? My current workflow was very easy: - snapshot - upgradesstables - drain and stop - backup configs - install new release - review config updates (patch existing config) - start Thanks --0000000000004ca6e80577cbbd0a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi list,

We recently upgrade= d our small cluster to the latest 3.0.17. Everything was nice and smooth, h= owever I am wondering if ti make sense to keep moving forward and upgarde t= o the latest 3.11.3?

We really need something like= the GROUP_BY and UFF/UDA seems limited wrt our use-case.
Does it make sense?
Any argument against?
I= s there any doc to prepare such upgrade?
My current workflow= was very easy:
- snapshot
- upgradesstables
= - drain and stop
- backup configs
- install new rel= ease
- review config updates (patch existing config)
- = start

Thanks
--0000000000004ca6e80577cbbd0a--