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 3FDAB200BC3 for ; Fri, 18 Nov 2016 13:06:37 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3E3E5160B04; Fri, 18 Nov 2016 12:06:37 +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 6468F160AFE for ; Fri, 18 Nov 2016 13:06:36 +0100 (CET) Received: (qmail 11266 invoked by uid 500); 18 Nov 2016 12:06:34 -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 11253 invoked by uid 99); 18 Nov 2016 12:06:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2016 12:06:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 785ABC1262 for ; Fri, 18 Nov 2016 12:06:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.898 X-Spam-Level: * X-Spam-Status: No, score=1.898 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] autolearn=disabled Authentication-Results: spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ICNxvESvhEGk for ; Fri, 18 Nov 2016 12:06:30 +0000 (UTC) Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com [209.85.218.47]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id CAD265F39B for ; Fri, 18 Nov 2016 12:06:29 +0000 (UTC) Received: by mail-oi0-f47.google.com with SMTP id 128so86224448oih.0 for ; Fri, 18 Nov 2016 04:06:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=YAVNNmjmMizcVqw8m9qEmBXFtVOeydV4A6we6AGzLzw=; b=WZ0eWOIHnHXGNmpR/Hf7fgq8GrA53kC70nWj9z8K0AWn2JHZEksJoHOMdB2ELk9gCo YZE3hYyXIS1rDoAvhBGj+vZWRnvMoh55YquHtbvhz4fhze4MbUbf7T/H4IwnYDtSayT0 bXnMert2EM6MZtnz2JITIMRDFygYP5mug4Fj8CRBPU74H+5N1+883DtLAsb7v/S3qfzk XIvHuNZSWaWoQlsUIApAE8r4gxghtGN8SmvbvXCn6NVJ0aRjb4Ef5vHlL/cIoCo7XeOe vGXJovMJsX/uK1/meX2BqbIqES8KwKKeRqXcIterZHnPQk7DFY8WlE+6e7knbThhhSqF w5AQ== 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:from:date :message-id:subject:to; bh=YAVNNmjmMizcVqw8m9qEmBXFtVOeydV4A6we6AGzLzw=; b=SdtxzjwE8B6uvXXrrqQ8appZcXv/B3YKE50YrnVoxNwow6q5/Wpga5DJla9i4fjlZZ osB2n3J0OjNwfXXssn+tz/Q9yVrtLUjm8bQvvCBUfKXDCVg+KRi2fI1Cr7MeRIVEXlJT zOkIbbdg7Qb7+hUme41+CYBmcMcOjCoWfkOi3qTxwL3ke2KgbWC3Pbj5vcXRZ98RPbL+ Hvfs2U3NCvDJl6YMDRRtpKEuh+TZNegKf22sFA4JOYrEX7pbiZUskxN/yAgHytglstiq dMjLeLNyWwfUHqYmXljDmlPEKpBhQ5WWQw08EZD8KmyyGlwH1XZAUrF6pT9c1Kj02xCq 7shg== X-Gm-Message-State: AKaTC01tNnf++NI8zQzMvB/rWSA5wgY8bqbugD23IGA8U5pFgZ6xsBjjTP4Cy9odMLkOkXKpwZq3V04ET928gQ== X-Received: by 10.157.0.74 with SMTP id 68mr4794084ota.249.1479470782649; Fri, 18 Nov 2016 04:06:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.112.196 with HTTP; Fri, 18 Nov 2016 04:06:02 -0800 (PST) In-Reply-To: <2016111818124392101825@zjqunshuo.com> References: <2016111817413017889017@zjqunshuo.com> <2016111818124392101825@zjqunshuo.com> From: Paulo Motta Date: Fri, 18 Nov 2016 10:06:02 -0200 Message-ID: Subject: Re: Is it a must to run Cassandra repair in scheduled time To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=94eb2c0328bc749a610541922248 archived-at: Fri, 18 Nov 2016 12:06:37 -0000 --94eb2c0328bc749a610541922248 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is an informative piece on (anti-entropy) repairs: https://cassandra-zone.com/understanding-repairs/ 2016-11-18 8:12 GMT-02:00 wxn002@zjqunshuo.com : > Thanks Ben for the response. It's very helpfull and it's really what I > want. > > > *From:* Ben Dalling > *Date:* 2016-11-18 18:07 > *To:* user > *Subject:* Re: Is it a must to run Cassandra repair in scheduled time > Hi Simon, > > See http://www.datastax.com/dev/blog/repair-in-cassandra for a good > explanation. Basically repair is not a good word because it suggests it = is > fixing something that is broken. This is not the case. It ensures the > consistency across your cluster. Not running repairs is a VERY BAD THING= . > Key things to check are how long do your repairs take and do they affect > the operation of your cluster. Decide how often and when to run them bas= ed > on this. The general rule of thumb is to run them within > the gc_grace_seconds. Another good article is *Cassandra=E2=80=99s =E2= =80=9CRepair=E2=80=9D > Should Be Called =E2=80=9CRequired Maintenance=E2=80=9D* which is availab= le at > https://lostechies.com/ryansvihla/2015/09/25/cassandras-repair-should-be- > called-required-maintenance/ > > Best wishes, > > Ben > > On 18 November 2016 at 09:41, wxn002@zjqunshuo.com > wrote: > >> Hi All, >> I'm new to Cassandra and from the mail chain seemed repair is an >> important thing to do. To avoid trouble in putting Cassandra in producti= on >> environment, I have some questions. >> 1. What exactly does Cassandra repair do? >> 2. I saw someone do repair in scheduled time, daily or weekly. Is it a >> must to do this? >> 3. In which cases do I need to do repair? >> >> Cheers, >> -Simon Wu >> > --94eb2c0328bc749a610541922248 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This is an informative piece on (anti-entropy) repairs:=C2= =A0https://ca= ssandra-zone.com/understanding-repairs/

2016-11-18 8:12 GMT-02:00 wxn002@zjqunshuo.com <wxn002@zjqunshuo.com>:
Thanks Ben for the response. It's very helpfull and i= t's really what I want.
=C2=A0
Date:=C2= =A02016-11-18=C2=A018:07
To:=C2=A0user
Subject:= =C2=A0Re: Is it a must to run Cassandra repair in scheduled time
Hi Simon,

See=C2=A0http://= www.datastax.com/dev/blog/repair-in-cassandra for a good explanati= on.=C2=A0 Basically repair is not a good word because it suggests it is fix= ing something that is broken.=C2=A0 This is not the case.=C2=A0 It ensures = the consistency across your cluster.=C2=A0 Not running repairs is a VERY BA= D THING.=C2=A0 Key things to check are how long do your repairs take and do= they affect the operation of your cluster.=C2=A0 Decide how often and when= to run them based on this.=C2=A0 The general rule of thumb is to run them = within the=C2=A0gc_grace_seconds.=C2=A0 Another good article is=C2=A0Cas= sandra=E2=80=99s =E2=80=9CRepair=E2=80=9D Should Be Called =E2=80=9CRequire= d Maintenance=E2=80=9D=C2=A0which is available at=C2=A0https://lostechies.com/ryansv= ihla/2015/09/25/cassandras-repair-should-be-called-required-maint= enance/

Best wishes,

Ben
On 18 November 2016 at 09:41, wxn002@zjqunshuo.com <wxn0= 02@zjqunshuo.com> wrote:
Hi All,
I'm new to Cassandra and from the m= ail chain seemed repair is an important thing to do. To avoid trouble in pu= tting Cassandra in production environment, I have some questions.
1. What exactly does Cassandra repair do?
2. I saw someone do re= pair in scheduled time, daily or weekly. Is it a must to do this?
3. In which cases do I need to do repair?

Cheers,=
-Simon Wu

--94eb2c0328bc749a610541922248--