Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B7073200B68 for ; Fri, 19 Aug 2016 11:26:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B59CD160AAC; Fri, 19 Aug 2016 09:26:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B1609160A8E for ; Fri, 19 Aug 2016 11:26:16 +0200 (CEST) Received: (qmail 82920 invoked by uid 500); 19 Aug 2016 09:26:15 -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 82910 invoked by uid 99); 19 Aug 2016 09:26:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Aug 2016 09:26:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C71151A522A for ; Fri, 19 Aug 2016 09:26:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.981 X-Spam-Level: * X-Spam-Status: No, score=1.981 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=foundev-pro.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id GHh6a40521b1 for ; Fri, 19 Aug 2016 09:26:12 +0000 (UTC) Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com [209.85.161.177]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9B48E5F30D for ; Fri, 19 Aug 2016 09:26:11 +0000 (UTC) Received: by mail-yw0-f177.google.com with SMTP id z8so9533390ywa.1 for ; Fri, 19 Aug 2016 02:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foundev-pro.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :references:in-reply-to:to; bh=kV76v0fjKPDJfIHSNSLmroDctnWtyQbyAybqpJCVnRQ=; b=QYHSjLI+BJEN50QQwN4YooRd0JVDktzTD7aQpK1OZSs/+5QeJ1RqYVhAAufdl4Wpn+ 0ERjDbrG+5jjntR5YmN+A68eA6p0VtNfqA5v7DOAFazZErRpAGI/e5ReyXS/3SEppafn eyVgegwHnyhS9lUC+OQoeYDu6M9zP9hhh4MQ0POc7586zANdzJF8jcP+rp1mgsa3+khd uDkqW3I9VEmeuztA03uE3joHqFCq197bnyzdP0UIFEmCMJzc3Z4Zflh+TzzA51Dz6b/J YIK5TrvK8HNsIbVqaqeZdcbNYh+W8gbQmk0ohci+dJyA533s/1wieor7il8fwHB9iB6a 3f9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:references:in-reply-to:to; bh=kV76v0fjKPDJfIHSNSLmroDctnWtyQbyAybqpJCVnRQ=; b=WuPIXLn/5oBAaOvYzBYfbuk7w+/1SJpj2Q8RI9Uhq2kG7W+jax/nux/iRl4S2m9Abp UhY5vtHtsYcRW1csWjbwGd5iqgn7SZHmel+PUCbqgN862+KLmT4R0I4irRFoqOwuOM/Y q0vneZ4JKJZfGk7VxwRbT8i2LQnpbXjgeMbJ31mksMju3D5x/wu+F2NJJNCZ3cByZc5A ISSGEQSln9cfYPK5okWgM7TPH12InbmlMnGY/tbQt9iTh41CUhGSNohgDYquIgvf48cX DL0IMMUCz1jxjvo0WSw/WQ2ze0yLy+CC8wcMvmwiiX+5AuqHYm/rVArGU83CvA0w6Smj 8bFg== X-Gm-Message-State: AEkooutEPAQTy/CxkrQ7pVpX78OTpuSFuwLqFnq3LbaWLGJbvPUK0iweSwxKXsJ+e9fvmA== X-Received: by 10.13.246.194 with SMTP id g185mr5805349ywf.31.1471598770400; Fri, 19 Aug 2016 02:26:10 -0700 (PDT) Received: from [10.0.1.41] (c-73-76-81-164.hsd1.tx.comcast.net. [73.76.81.164]) by smtp.gmail.com with ESMTPSA id t134sm1241767ywc.54.2016.08.19.02.26.08 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 19 Aug 2016 02:26:08 -0700 (PDT) From: Ryan Svihla Content-Type: multipart/alternative; boundary=Apple-Mail-C55ABB11-C451-4CD7-89FD-CEDEAA59E786 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Subject: Re: A question to updatesstables Message-Id: <98A9DEE5-4425-43EF-B12B-81F7A083B780@foundev.pro> Date: Fri, 19 Aug 2016 04:26:08 -0500 References: <76B23E0F09982343A088AB6D02883DEB16BDD5@MX201CL02.corp.emc.com> <76B23E0F09982343A088AB6D02883DEB16DC17@MX201CL02.corp.emc.com> In-Reply-To: <76B23E0F09982343A088AB6D02883DEB16DC17@MX201CL02.corp.emc.com> To: user@cassandra.apache.org X-Mailer: iPhone Mail (13G35) archived-at: Fri, 19 Aug 2016 09:26:17 -0000 --Apple-Mail-C55ABB11-C451-4CD7-89FD-CEDEAA59E786 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The actual error message could be very useful to diagnose the reason. There a= re warnings about incompatible formats which are safe to ignore (usually in t= he cache) and I have one time seen an issue with commit log archiving preven= ting a startup during upgrade. Usually there is something else broken and th= e version mismatch is a false signal. Regards, Ryan Svihla > On Aug 18, 2016, at 10:18 PM, Lu, Boying wrote: >=20 > Thanks a lot. > =20 > I=E2=80=99m a little bit of confusing. If the =E2=80=98nodetool updatesst= able=E2=80=99 doesn=E2=80=99t work without Cassandra server running, > and Cassandra server failed to start due to the incompatible SSTable forma= t, how to resolve this dilemma? > =20 > =20 > =20 > From: Carlos Alonso [mailto:info@mrcalonso.com]=20 > Sent: 2016=E5=B9=B48=E6=9C=8818=E6=97=A5 18:44 > To: user@cassandra.apache.org > Subject: Re: A question to updatesstables > =20 > Replies inline >=20 > Carlos Alonso | Software Engineer | @calonso > =20 > On 18 August 2016 at 11:56, Lu, Boying wrote: > Hi, All, > =20 > We use Cassandra in our product. I our early release we use Cassandra 1.2.= 10 whose SSTable is =E2=80=98ic=E2=80=99 format. > We upgrade Cassandra to 2.0.10 in our product release. But the Cassandra s= erver failed to start due to the > incompatible SSTable format and the log message told us to use =E2=80=98no= detool updatesstables=E2=80=99 to upgrade SSTable files. > =20 > To make sure that no negative impact on our data, I want to confirm follow= ing things about this command before trying it: > 1. Does it work without Cassandra server running? >=20 > No, it won't.=20 > 2. Will it cause data lost with this command? >=20 > It shouldn't if you followed the upgrade instructions properly > 3. What=E2=80=99s the best practice to void this error occurs again (= e.g. upgrading Cassandra next time)? >=20 > Upgrading SSTables is required or not depending on the upgrade you're runn= ing, basically if the SSTables layout changes you'll need to run it and not o= therwise so there's nothing you can do to avoid it=20 > =20 > Thanks > =20 > Boying > =20 --Apple-Mail-C55ABB11-C451-4CD7-89FD-CEDEAA59E786 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
The actual error message could be very= useful to diagnose the reason. There are warnings about incompatible format= s which are safe to ignore (usually in the cache) and I have one time seen a= n issue with commit log archiving preventing a startup during upgrade. Usual= ly there is something else broken and the version mismatch is a false signal= .

Regards,

Ryan S= vihla

On Aug 18, 2016, at 10:18 PM, Lu, Boying <Boying.Lu@emc.com> wrote:

Thanks a lot.

 

I=E2=80=99m a little bit of= confusing.  If the =E2=80=98nodetool updatesstable=E2=80=99 doesn=E2=80= =99t work without Cassandra server running,

and Cassandra server failed= to start due to the incompatible SSTable format,  how to resolve this d= ilemma?

 

 

 

From: Carlos Alon= so [mailto:info@mrcalonso.com]
Sent: 2016=E5=B9=B48=E6=9C=8818=E6=97=A5 18:44
To: user@cassandra.apach= e.org
Subject: Re: A question to updatesstables

 

Replies inline


Carlos Alonso | Softw= are Engineer | @calonso

 

On 18 August 2016 at 11:56, Lu, Boying <Boying.Lu@emc.com> wrote= :

Hi, All,

 

We use Cassandra in our product. I o= ur early release we use Cassandra 1.2.10 whose SSTable is =E2=80=98ic=E2=80=99= format.

We upgrade Cassandra to 2.0.10 in o= ur product release. But the Cassandra server failed to start due to the

incompatible SSTable format and the= log message told us to use =E2=80=98nodetool updatesstables=E2=80=99 to upg= rade SSTable files.

 

To make sure that no negative impac= t on our data, I want to confirm following things about this command before t= rying it:

1.       Does it work without Cassandra serve= r running?

No, it won't. 

2.       Will it cause data lost with this co= mmand?

It shouldn't if you followed the upgrade instructions= properly

3.       What=E2=80=99s the best practice to void this error occurs agai= n (e.g. upgrading Cassandra next time)?

Upgrading SSTables is required or not depending on th= e upgrade you're running, basically if the SSTables layout changes you'll ne= ed to run it and not otherwise so there's nothing you can do to avoid it&nbs= p;

 

Thanks

 

Boying

 

= --Apple-Mail-C55ABB11-C451-4CD7-89FD-CEDEAA59E786--