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 4DA5A200BF7 for ; Mon, 9 Jan 2017 09:23:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4C200160B3E; Mon, 9 Jan 2017 08:23:41 +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 6D357160B3B for ; Mon, 9 Jan 2017 09:23:40 +0100 (CET) Received: (qmail 28069 invoked by uid 500); 9 Jan 2017 08:23:38 -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 28059 invoked by uid 99); 9 Jan 2017 08:23:38 -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; Mon, 09 Jan 2017 08:23:38 +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 690A3180140 for ; Mon, 9 Jan 2017 08:23:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_REPLY=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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6jKpQ5YL0Iw5 for ; Mon, 9 Jan 2017 08:23:37 +0000 (UTC) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8476B5F4A6 for ; Mon, 9 Jan 2017 08:23:36 +0000 (UTC) Received: by mail-lf0-f51.google.com with SMTP id m78so68429172lfg.2 for ; Mon, 09 Jan 2017 00:23:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=34w6nL6WHVMjo15umVPExlz7s8fjBF2jVZGZJWgnlLg=; b=ngMAJwyTfrHCbUqE3Vcmuwvdaz93pqL6PFM9aqhwa4jhYKWvLOp3LzC0wAk3GGcfYW uKitNQflXXC/vbKFUHbtEehYAFRNgBO5vAc+YBqrkGnrUcq9gwWBAZcLV/c+evcu7YZu Sbv1e3IQlJVPoriNY6aXMuAVqcLaNMDSAne6JyNHn5BFxrD1GGCkQxx9FLZgM27c95tS wGXY8BxtkuHicRYDDolnAm2MGH0umBdjcdFHBXUrwevLhVKH+ygqBMGDnrBJ00H9DzLs icMY/0bw/G/TTFDudQt1UhtR0Rmg229dCUfyciKMow226IfrMFZfq6Tfw8bM2sR/1GVX Dt1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=34w6nL6WHVMjo15umVPExlz7s8fjBF2jVZGZJWgnlLg=; b=WfJZcmD5PuPnaVkabhsT3Czhg6XugLkIQcH8OlmcSJdbDPB5IZPP7/1y4W/ioWsunX stFzmBRlaTHHKgFdxKvcnEUGKPZOV9ZfdR95yc6mEKhnUIm0zYIEGacRuDNtSHdP9U2T DFe3lJ4d+pv39hQY6EjFEB0epKSDd9ZgPBy1iyxs5nAsal3ugSJdgiQtRqr6YBDo/cu7 +sIP/xm769I4IagalhOQNs05qqKaQdGpkUwuMZhrOANo3si2WfKsoOIC02H5z4XtDRpl osRNWqJQ9gTq7UHGBxbAdii2TemrZ2BBIsXaNK551E4FCoE0Y/Ote+prPn+gaBtPqeQ0 YiZA== X-Gm-Message-State: AIkVDXLlYhlSK6Cd5j3sdSXvv5MOnYJLEx7Aaw0PzLpcJgm99p28HVu59gG1gD8NZdwqSw== X-Received: by 10.25.67.83 with SMTP id m19mr29531122lfj.137.1483950208790; Mon, 09 Jan 2017 00:23:28 -0800 (PST) Received: from [100.96.50.93] (host-95-199-18-93.mobileonline.telia.com. [95.199.18.93]) by smtp.gmail.com with ESMTPSA id x75sm16273971lfi.16.2017.01.09.00.23.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Jan 2017 00:23:27 -0800 (PST) From: Oskar Kjellin Content-Type: multipart/alternative; boundary=Apple-Mail-9156C3AC-2573-48B1-9D6C-D8957DE30CDB Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Mon, 9 Jan 2017 09:23:26 +0100 Subject: Re: Incremental repair for the first time Message-Id: References: In-Reply-To: To: user@cassandra.apache.org X-Mailer: iPhone Mail (14C92) archived-at: Mon, 09 Jan 2017 08:23:41 -0000 --Apple-Mail-9156C3AC-2573-48B1-9D6C-D8957DE30CDB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable There is no harm in running it tho. If it's not needed it will simply termin= ate. Better to be safe Sent from my iPhone > On 9 Jan 2017, at 08:13, Amit Singh F wrote: >=20 > Hi , > =20 > Generally Upgradesstables are only recommended when you plan to move with M= ajor version like from 2.0 to 2.1 or from 2.1 to 2.2 etc. Since you are do= ing minor version upgrade no need to run upgradesstables utility. > =20 > Link by Datastax might be helpful to you : > =20 > https://support.datastax.com/hc/en-us/articles/208040036-Nodetool-upgrades= stables-FAQ > =20 > From: Kathiresan S [mailto:kathiresanselvaraj@gmail.com]=20 > Sent: Wednesday, January 04, 2017 12:22 AM > To: user@cassandra.apache.org > Subject: Re: Incremental repair for the first time > =20 > Thank you! > =20 > We are planning to upgrade to 3.0.10 for this issue. > =20 > =46rom the NEWS txt file (https://github.com/apache/cassandra/blob/trunk/N= EWS.txt), it looks like there is no need for sstableupgrade when we upgrade f= rom 3.0.4 to 3.0.10 (i.e. Just installing 3.0.10 Cassandra would suffice and= it will work with the sstables created by 3.0.4 ?) > =20 > Could you please confirm (if i'm reading the upgrade instructions correctl= y)? > =20 > Thanks, > Kathir > =20 > On Tue, Dec 20, 2016 at 5:28 PM, kurt Greaves wrote= : > No workarounds, your best/only option is to upgrade (plus you get the bene= fit of loads of other bug fixes). > =20 > On 16 December 2016 at 21:58, Kathiresan S w= rote: > Thank you! > =20 > Is any work around available for this version?=20 > =20 > Thanks, > Kathir >=20 >=20 > On Friday, December 16, 2016, Jake Luciani wrote: > This was fixed post 3.0.4 please upgrade to latest 3.0 release > =20 > On Fri, Dec 16, 2016 at 4:49 PM, Kathiresan S wrote: > Hi, > =20 > We have a brand new Cassandra cluster (version 3.0.4) and we set up nodeto= ol repair scheduled for every day (without any options for repair). As per d= ocumentation, incremental repair is the default in this case.=20 > Should we do a full repair for the very first time on each node once and t= hen leave it to do incremental repair afterwards? > =20 > Problem we are facing: > =20 > On a random node, the repair process throws validation failed error, point= ing to some other node > =20 > For Eg. Node A, where the repair is run (without any option), throws below= error > =20 > Validation failed in /Node B > =20 > In Node B when we check the logs, below exception is seen at the same exac= t time... > =20 > java.lang.RuntimeException: Cannot start multiple repair sessions over the= same sstables > at org.apache.cassandra.db.compaction.CompactionManager.doValidati= onCompaction(CompactionManager.java:1087) ~[apache-cassandra-3.0.4.jar:3.0.4= ] > at org.apache.cassandra.db.compaction.CompactionManager.access$700= (CompactionManager.java:80) ~[apache-cassandra-3.0.4.jar:3.0.4] > at org.apache.cassandra.db.compaction.CompactionManager$10.call(Co= mpactionManager.java:700) ~[apache-cassandra-3.0.4.jar:3.0.4] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1= .8.0_73] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExe= cutor.java:1142) ~[na:1.8.0_73] > =20 > Can you please help on how this can be fixed? > =20 > Thanks, > Kathir >=20 >=20 >=20 > -- > http://twitter.com/tjake > =20 > =20 --Apple-Mail-9156C3AC-2573-48B1-9D6C-D8957DE30CDB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
There is no harm in running it tho. If it's not needed it will simply terminate. Better to be safe

Sent from my iPhone

On 9 Jan 2017, at 08:13, Amit Singh F <amit.f.singh@ericsson.com> wrote:

Hi ,

 

Generally Upgradesstables are only recommended when you plan to move with Major version like  from 2.0 to 2.1  or from 2.1 to 2.2 etc. Since you are doing minor version upgrade no need to run upgradesstables utility.

 

Link by Datastax might be helpful to you :

 

https://support.datastax.com/hc/en-us/articles/208040036-Nodetool-upgradesstables-FAQ

 

From: Kathiresan S [mailto:kathiresanselvaraj@gmail.com]
Sent: Wednesday, January 04, 2017 12:22 AM
To: user@cassandra.apache.org
Subject: Re: Incremental repair for the first time

 

Thank you!

 

We are planning to upgrade to 3.0.10 for this issue.

 

From the NEWS txt file (https://github.com/apache/cassandra/blob/trunk/NEWS.txt), it looks like there is no need for sstableupgrade when we upgrade from 3.0.4 to 3.0.10 (i.e. Just installing 3.0.10 Cassandra would suffice and it will work with the sstables created by 3.0.4 ?)

 

Could you please confirm (if i'm reading the upgrade instructions correctly)?

 

Thanks,

Kathir

 

On Tue, Dec 20, 2016 at 5:28 PM, kurt Greaves <kurt@instaclustr.com> wrote:

No workarounds, your best/only option is to upgrade (plus you get the benefit of loads of other bug fixes).

 

On 16 December 2016 at 21:58, Kathiresan S <kathiresanselvaraj@gmail.com> wrote:

Thank you!

 

Is any work around available for this version? 

 

Thanks,

Kathir



On Friday, December 16, 2016, Jake Luciani <jakers@gmail.com> wrote:

This was fixed post 3.0.4 please upgrade to latest 3.0 release

 

On Fri, Dec 16, 2016 at 4:49 PM, Kathiresan S <kathiresanselvaraj@gmail.com> wrote:

Hi,

 

We have a brand new Cassandra cluster (version 3.0.4) and we set up nodetool repair scheduled for every day (without any options for repair). As per documentation, incremental repair is the default in this case. 

Should we do a full repair for the very first time on each node once and then leave it to do incremental repair afterwards?

 

Problem we are facing:

 

On a random node, the repair process throws validation failed error, pointing to some other node

 

For Eg. Node A, where the repair is run (without any option), throws below error

 

Validation failed in /Node B

 

In Node B when we check the logs, below exception is seen at the same exact time...

 

java.lang.RuntimeException: Cannot start multiple repair sessions over the same sstables

        at org.apache.cassandra.db.compaction.CompactionManager.doValidationCompaction(CompactionManager.java:1087) ~[apache-cassandra-3.0.4.jar:3.0.4]

        at org.apache.cassandra.db.compaction.CompactionManager.access$700(CompactionManager.java:80) ~[apache-cassandra-3.0.4.jar:3.0.4]

        at org.apache.cassandra.db.compaction.CompactionManager$10.call(CompactionManager.java:700) ~[apache-cassandra-3.0.4.jar:3.0.4]

        at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_73]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_73]

 

Can you please help on how this can be fixed?

 

Thanks,

Kathir




--

 

 

--Apple-Mail-9156C3AC-2573-48B1-9D6C-D8957DE30CDB--