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 0A3221759C for ; Tue, 20 Oct 2015 20:31:33 +0000 (UTC) Received: (qmail 32925 invoked by uid 500); 20 Oct 2015 20:31:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 32884 invoked by uid 500); 20 Oct 2015 20:31:17 -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 32868 invoked by uid 99); 20 Oct 2015 20:31:17 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2015 20:31:17 +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 6FE93C394F for ; Tue, 20 Oct 2015 20:31:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id MWPIMaanFfS2 for ; Tue, 20 Oct 2015 20:31:12 +0000 (UTC) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 5D22920594 for ; Tue, 20 Oct 2015 20:31:11 +0000 (UTC) Received: by lbbes7 with SMTP id es7so24107557lbb.2 for ; Tue, 20 Oct 2015 13:31:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=pWpezWZHENN1hTxpSny56WMTKSpWn6d9XUj43bW1Vfg=; b=gQwrRne+6OrMOvqAyLTpC3FSpcfWN79WR2+6ZBcTE2Q12REyf66Ae3nodsel247K5B 73K5+1gcm1MMh01k2yyPN8bXXnWD6xNkHGdU5R8m86S1Xd4wfZn5kO/XDkB01SoIYZv/ bML6FY7vHOeLfwiDaVkw14OX2v4Cx8SQo6NYMgMeKjB7BgUxOQms2UskL0l5uo+ACcn9 HUQeNZs6Kr3dkMADOnrOFOnZtd/vUKi8Mlr0aWW9Z2YB3tCQ/CIp2qc4fJL0TrxA0s93 uolU7oPBZGvOwQZ2IcIFN5+k+SZR46TURMXNibNP4wijGkuMgemvxG7e23Ru+UsjYifT r8Hg== X-Gm-Message-State: ALoCoQk5rlEZVyNO5zEghjcOJ+3/j724J0nWqcshG3t6JkPpRyUfYphvC6d+H41c19UCVb0TUArv MIME-Version: 1.0 X-Received: by 10.112.198.37 with SMTP id iz5mr3082006lbc.44.1445373065057; Tue, 20 Oct 2015 13:31:05 -0700 (PDT) Received: by 10.114.28.137 with HTTP; Tue, 20 Oct 2015 13:31:04 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Oct 2015 13:31:04 -0700 Message-ID: Subject: Re: Would we have data corruption if we bootstrapped 10 nodes at once? From: Robert Coli To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11c2a40c1c750d05228f243f --001a11c2a40c1c750d05228f243f Content-Type: text/plain; charset=UTF-8 On Tue, Oct 20, 2015 at 9:13 AM, Branton Davis wrote: > >> Just to clarify, I was thinking about a scenario/disaster where we lost > the entire cluster and had to rebuild from backups. I assumed we would > start each node with the backed up data and commit log directories already > there and with auto_bootstrap=false, and I also hoped that we could do all > nodes at once, since they each already had their data. Is that wrong? If > so, how would you handle such a situation? > "The one case I can imagine is when you are starting a cluster which is not receiving any write traffic and does contain snapshots. " The case you describe is in that class of cases. =Rob > > --001a11c2a40c1c750d05228f243f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Oct 20, 2015 at 9:13 AM, Branton Davis <branton.davis@spannin= g.com> wrote:

Just to= clarify, I was thinking about a scenario/disaster where we lost the entire= cluster and had to rebuild from backups.=C2=A0 I assumed we would start ea= ch node with the backed up data and commit log directories already there an= d with auto_bootstrap=3Dfalse, and I also hoped that we could do all nodes = at once, since they each already had their data.=C2=A0 Is that wrong?=C2=A0= If so, how would you handle such a situation?

"The one case I can imagine is when you are starting a clus= ter which is not receiving any write traffic and does contain snapshots. &q= uot;

The case you describe is in that class of cases.

=3DRo= b

=C2=A0
=C2=A0

--001a11c2a40c1c750d05228f243f--