Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6D1AC11AD4 for ; Fri, 19 Sep 2014 18:27:16 +0000 (UTC) Received: (qmail 84252 invoked by uid 500); 19 Sep 2014 18:27:14 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 84227 invoked by uid 500); 19 Sep 2014 18:27:14 -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 84217 invoked by uid 99); 19 Sep 2014 18:27:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 18:27:13 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_IMAGE_ONLY_32,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of burtonator2011@gmail.com designates 209.85.215.52 as permitted sender) Received: from [209.85.215.52] (HELO mail-la0-f52.google.com) (209.85.215.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 18:26:48 +0000 Received: by mail-la0-f52.google.com with SMTP id gq15so3606704lab.25 for ; Fri, 19 Sep 2014 11:26:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=3LYA4g57nW/f34Ar/V9U9JsnCa7pxXGCV1UZU07CQeA=; b=CGwonCwclqadY3mXuRWrDbNWAG8E+OUmcRpsmKv5hDmqjIStRdzexJYvcP02ayz0dx 3hGbW9WUl0yZAOmJbuzixQmARIYhQXEpFrQjnG5nUgOITVXpqOqw+jKdxEaGyEMGRmt3 mmTSupeV1zTE5xf/C3W05X3EwJq5WBnX2yneySYdTzaO31d+ejWGqwp5cWD7IGzJOAwr fTWKmrQ9FjBSa32gjulZN2ZcKGGr0O/FXbIRXop+Lc2k4TTnOPRgLY9fsmZbRp7nsSKn 5rqn3LZo5bnY4oPsd4/As1do4bqXwqGfAx9v9lVye73t/os0Hl60vDTSdUPkxekh1VaE lu+w== X-Received: by 10.152.3.130 with SMTP id c2mr8623561lac.72.1411151207863; Fri, 19 Sep 2014 11:26:47 -0700 (PDT) MIME-Version: 1.0 Sender: burtonator2011@gmail.com Received: by 10.112.210.101 with HTTP; Fri, 19 Sep 2014 11:26:27 -0700 (PDT) In-Reply-To: <54187CE0.7080501@gmail.com> References: <54187CE0.7080501@gmail.com> From: Kevin Burton Date: Fri, 19 Sep 2014 11:26:27 -0700 X-Google-Sender-Auth: _yUKioO3Nqwc4nk8ixWySC6a1BU Message-ID: Subject: Re: Blocking while a node finishes joining the cluster after restart. To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=089e014933927817de05036f3e8e X-Virus-Checked: Checked by ClamAV on apache.org --089e014933927817de05036f3e8e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Hi Kevin, if you are using the latest version of opscenter, then even the community (=3D free) edition can do a rolling restart of your cluster. It'= s pretty convenient. We=E2=80=99re using ansible so I=E2=80=99d like something that integrates w= ith that=E2=80=A6 On Tue, Sep 16, 2014 at 11:09 AM, Duncan Sands wrote: > Hi Kevin, if you are using the latest version of opscenter, then even the > community (=3D free) edition can do a rolling restart of your cluster. I= t's > pretty convenient. > > Ciao, Duncan. > > On 16/09/14 19:44, Kevin Burton wrote: > >> Say I want to do a rolling restart of Cassandra=E2=80=A6 >> >> I can=E2=80=99t just restart all of them because they need some time to = gossip >> and for >> that gossip to get to all nodes. >> >> What is the best strategy for this. >> >> It would be something like: >> >> /etc/init.d/cassandra restart && wait-for-cassandra.sh >> >> =E2=80=A6 or something along those lines. >> >> -- >> >> Founder/CEO Spinn3r.com >> Location: *San Francisco, CA* >> blog:**http://burtonator.wordpress.com >> =E2=80=A6 or check out my Google+ profile >> >> >> >> > --=20 Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com =E2=80=A6 or check out my Google+ profile --089e014933927817de05036f3e8e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>=C2=A0Hi Kevin, if you are using the latest version of opscenter, the= n even the community (=3D free) edition can do a rolling restart of your cl= uster.=C2=A0 It's pretty convenient.

We=E2=80=99re using ansible so I=E2=80=99d like something = that integrates=C2=A0with that=E2=80=A6=C2=A0

On Tue, Sep 16, 2014 at 11:= 09 AM, Duncan Sands <duncan.sands@gmail.com> wrote:
=
Hi Kevin, if you are using the latest versio= n of opscenter, then even the community (=3D free) edition can do a rolling= restart of your cluster.=C2=A0 It's pretty convenient.

Ciao, Duncan.

On 16/09/14 19:44, Kevin Burton wrote:
Say I want to do a rolling restart of Cassandra=E2=80=A6

I can=E2=80=99t just restart all of them because they need some time to gos= sip and for
that gossip to get to all nodes.

What is the best strategy for this.

It would be something like:

/etc/init.d/cassandra restart && wait-for-cassandra.sh

=E2=80=A6 or something along those lines.

--

 Founder/CEO Spinn3r.com <http://Spinn3r.com>
Location: *San Francisco, CA*
blog:**http:/= /burtonator.wordpress.com
=E2=80=A6 or check out my Google+ profile
 <https://plus.google.com/102718274791889610666/posts&= gt;
<http://spinn3r.com= >





--

Founder/CEO=C2=A0Spinn3r.com
Location:=C2=A0San Fra= ncisco, CA
=E2=80=A6 or check out my Goo= gle+ profile

=
--089e014933927817de05036f3e8e--