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 EB6C8200CD2 for ; Thu, 27 Jul 2017 19:37:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E9DDA16B2E8; Thu, 27 Jul 2017 17:37:44 +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 141A016B2DD for ; Thu, 27 Jul 2017 19:37:43 +0200 (CEST) Received: (qmail 86161 invoked by uid 500); 27 Jul 2017 17:37:42 -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 86151 invoked by uid 99); 27 Jul 2017 17:37:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2017 17:37:42 +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 D0E38C2CDF for ; Thu, 27 Jul 2017 17:37:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.9 X-Spam-Level: * X-Spam-Status: No, score=1.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id O9DbOJOb3Hiu for ; Thu, 27 Jul 2017 17:37:31 +0000 (UTC) Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com [209.85.192.182]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6CB135F6C0 for ; Thu, 27 Jul 2017 17:37:30 +0000 (UTC) Received: by mail-pf0-f182.google.com with SMTP id z129so46655677pfb.3 for ; Thu, 27 Jul 2017 10:37:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=8dKBxnMURx2RlrSF+mnEBkJYkgnw+DIRlAKw4wk24ec=; b=S2zPaeqCqFnnoU4SWk1ilBkYUrv7P1LVmD+3FlqHGlHoJkQrZpiMB6DCK6gFBlgAgl YVYs8oed0KPJrLXRi7DpJkuJDsSN7jrhFsRRLiRZWjLVA6swjuECdd1qoRw+i45Zysp5 7eCEX7l3EBahopL+AtGQE6OYRO0++pouyGTdP5Fim37mLAxtofEx1dhWW2j7HV2SPLsA TKcJo3NxY/IxZuUrooiTzSl3aIz/A5kUf66pFPTaA7MjxWsr9RXTyM2qdbulmBXA83lI 0fR0BpSxn7/0oK2muR7ktDxQ7Guaezd95CBGML/1zdZgsR454nUm+18/Gv6I1T8iIxpM UmVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=8dKBxnMURx2RlrSF+mnEBkJYkgnw+DIRlAKw4wk24ec=; b=dybGuDc04Zud06yejb+Nj1yZcoubRRMPZ4GhZlAgZ459TcE8sFd3IgrdaGAq1OnKgB 8bPaSUeY3OFnkJHECS8A5iOVGDHfNNvKRNjYon7rDnBDEkP7ScQNY/khWWQd31H4Iwv9 UO5tkoPEOMB/cayzorzUCMyuHVsJu44Yz8q156T2qsspWy/1/izqthY5fcogj4jLGMXm psrUTy1TIJgrosEQHXZQbDc5H+U2gOpIHZisuKhbgvFi9SiAM2OGvntZ4uNkUSpkI+Pd pXUVP5PsUx5OF2FMZsD37/JyOJ6lnsCByf7JTv6JpmrXZzwOtfnE5m+OIs6MjSb5s0Dv 3V0Q== X-Gm-Message-State: AIVw113qUvtx0mb2NLOLZARDerBzT6EQ3OT8q/1InhAPFQ8q1qPTGF6t E7tWelxX+rXttp8fCnk= X-Received: by 10.84.210.203 with SMTP id a69mr5186523pli.399.1501177048743; Thu, 27 Jul 2017 10:37:28 -0700 (PDT) Received: from beast.fios-router.home ([47.144.143.186]) by smtp.gmail.com with ESMTPSA id s11sm14407862pfi.24.2017.07.27.10.37.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Jul 2017 10:37:27 -0700 (PDT) From: Jon Haddad Content-Type: multipart/alternative; boundary="Apple-Mail=_143EBADB-0689-41C7-9013-62B047C37970" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Data Loss irreparabley so Date: Thu, 27 Jul 2017 10:37:26 -0700 References: <3B5C1F67-F432-46AE-8D2D-E79D5FE30765@pandora.com> To: user In-Reply-To: Message-Id: <61557BF6-93F1-4282-BAC1-65A678A88BFE@gmail.com> X-Mailer: Apple Mail (2.3273) archived-at: Thu, 27 Jul 2017 17:37:45 -0000 --Apple-Mail=_143EBADB-0689-41C7-9013-62B047C37970 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 We (The Last Pickle) maintain an open source tool to help manage repairs = across your clusters called Reaper. It=E2=80=99s a lot easier to set up = and manage than trying to manage it through cron. http://thelastpickle.com/reaper.html = > On Jul 27, 2017, at 12:38 AM, Daniel H=C3=B6lbling-Inzko = wrote: >=20 > In that vein, Cassandra support Auto compaction and incremental = repair.=20 > Does this mean I have to set up cron jobs on each node to do a = nodetool repair or is this taken care of by Cassandra anyways? > How often should I run nodetool repair >=20 > Greetings Daniel > Jeff Jirsa > schrieb am = Do. 27. Juli 2017 um 07:48: >=20 >=20 > On 2017-07-25 15:49 (-0700), Roger Warner > wrote: > > This is a quick informational question. I know that Cassandra = can detect failures of nodes and repair them given replication and = multiple DC. > > > > My question is can Cassandra tell if data was lost after a failure = and node(s) =E2=80=9Cfixed=E2=80=9D and resumed operation? > > >=20 > Sorta concerned by the way you're asking this - Cassandra doesn't = "fix" failed nodes. It can route requests around a down node, but the = "fixing" is entirely manual. >=20 > If you have a node go down temporarily, and it comes back up (with = it's disk intact), you can see it "repair" data with a combination of = active (anti-entropy) repair via nodetool repair, or by watching = 'nodetool netstats' and see the read repair counters increase over time = (which will happen naturally as data is requested and mismatches are = detected in the data, based on your consistency level). >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org = > For additional commands, e-mail: user-help@cassandra.apache.org = >=20 --Apple-Mail=_143EBADB-0689-41C7-9013-62B047C37970 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
We (The Last Pickle) maintain an open source = tool to help manage repairs across your clusters called Reaper. =  It=E2=80=99s a lot easier to set up and manage than trying to = manage it through cron.

http://thelastpickle.com/reaper.html

On = Jul 27, 2017, at 12:38 AM, Daniel H=C3=B6lbling-Inzko <daniel.hoelbling-inzko@bitmovin.com> wrote:

In that vein, = Cassandra support Auto compaction and incremental repair.
Does this mean I have to set up cron jobs on each node to do = a nodetool repair or is this taken care of by Cassandra anyways?
How often should I run nodetool repair

Greetings Daniel
Jeff Jirsa <jjirsa@apache.org> schrieb am Do. 27. Juli 2017 um = 07:48:


On 2017-07-25 15:49 (-0700), Roger Warner <rwarner@pandora.com> wrote:
> This is a quick informational question.     I know = that Cassandra can detect failures of nodes and repair them given = replication and multiple DC.
>
> My question is can Cassandra tell if data was lost after a failure = and node(s) =E2=80=9Cfixed=E2=80=9D and resumed operation?
>

Sorta concerned by the way you're asking this - Cassandra doesn't "fix" = failed nodes. It can route requests around a down node, but the "fixing" = is entirely manual.

If you have a node go down temporarily, and it comes back up (with it's = disk intact), you can see it "repair" data with a combination of active = (anti-entropy) repair via nodetool repair, or by watching 'nodetool = netstats' and see the read repair counters increase over time (which = will happen naturally as data is requested and mismatches are detected = in the data, based on your consistency level).



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org


= --Apple-Mail=_143EBADB-0689-41C7-9013-62B047C37970--