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 9F368200CE0 for ; Thu, 27 Jul 2017 07:48:51 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9DAA916A395; Thu, 27 Jul 2017 05:48:51 +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 E27BB16A390 for ; Thu, 27 Jul 2017 07:48:50 +0200 (CEST) Received: (qmail 35021 invoked by uid 500); 27 Jul 2017 05:48:49 -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 35012 invoked by uid 99); 27 Jul 2017 05:48:48 -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; Thu, 27 Jul 2017 05:48:48 +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 91099C02AA for ; Thu, 27 Jul 2017 05:48:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=6.31 tests=[FROM_MISSPACED=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled 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 grktxOAoV759 for ; Thu, 27 Jul 2017 05:48:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A70565FC9D for ; Thu, 27 Jul 2017 05:48:47 +0000 (UTC) Received: from localhost (cust-asf.ponee.io [163.172.22.183]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 455F3E00A3 for ; Thu, 27 Jul 2017 05:48:45 +0000 (UTC) MIME-Version: 1.0 Message-ID: Subject: Re: Data Loss irreparabley so References: <3B5C1F67-F432-46AE-8D2D-E79D5FE30765@pandora.com> From: "Jeff Jirsa" In-Reply-To: <3B5C1F67-F432-46AE-8D2D-E79D5FE30765@pandora.com> Content-Type: text/plain; charset="iso-8859-1" x-ponymail-sender: cb367aa5aed1991b197e48bcdd89864c2a894a70 Date: Thu, 27 Jul 2017 05:48:44 -0000 x-ponymail-agent: PonyMail Composer/0.2 To: X-Mailer: LuaSocket 3.0-rc1 archived-at: Thu, 27 Jul 2017 05:48:51 -0000 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) “fixed” 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