Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0AD4119F6 for ; Fri, 10 May 2013 18:25:28 +0000 (UTC) Received: (qmail 51639 invoked by uid 500); 10 May 2013 18:25:26 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 51618 invoked by uid 500); 10 May 2013 18:25:26 -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 51610 invoked by uid 99); 10 May 2013 18:25:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 18:25:25 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rcoli@eventbrite.com designates 209.85.216.170 as permitted sender) Received: from [209.85.216.170] (HELO mail-qc0-f170.google.com) (209.85.216.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2013 18:25:19 +0000 Received: by mail-qc0-f170.google.com with SMTP id s11so2433117qcw.15 for ; Fri, 10 May 2013 11:24:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=gdv+16fnczwqU8Esz5iurv0VQpZdb8kQCsj3fEOf44w=; b=ItSzCDT8QiMd9AtP9tVv/TEfMp87+qtsLYXCbAqwhXaWbq3sxglmmwqDrrah95Itl5 4pipJmVG/yBzQs2CdjaD5ZlSdsM2Q8rm9pVEw2arztXpQhLTwJTqGQtQLf/hSPeoUnbF n/KtjgebPoY0uL6rg1+BSKgi5VMPDlFcaQIo7QunBrJ9M9M9iReP9HgRXrtZTXr6lltD 2nbNbyLmzMMoHm+4S4poZwTEa7N6MPCNzf1xiggvKL5ylctOarVG1NnCIdxfh9xucrKe j88K0kHq2/5UdPvf9vS4wE8xPLTU8ZzXqYXINHnn+aCirx/fzrJo41n2lpe52XRbeaVb Evuw== MIME-Version: 1.0 X-Received: by 10.229.103.93 with SMTP id j29mr1975539qco.47.1368210298112; Fri, 10 May 2013 11:24:58 -0700 (PDT) Received: by 10.49.104.141 with HTTP; Fri, 10 May 2013 11:24:58 -0700 (PDT) Date: Fri, 10 May 2013 11:24:58 -0700 Message-ID: Subject: (unofficial) Community Poll for Production Operators : Repair From: Robert Coli To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlbH6veQpgVAXvZtOF0mae6QrK72R3StSCA1Dgzs95jfZOy/hJayFYoEVm9bmc/kgklw17t X-Virus-Checked: Checked by ClamAV on apache.org Hi! I have been wondering how Repair is actually used by operators. If people operating Cassandra in production could answer the following questions, I would greatly appreciate it. 1) What version of Cassandra do you run, on what hardware? 2) What consistency level do you write at? Do you do DELETEs? 3) Do you run a regularly scheduled repair? 4) If you answered "yes" to 3, what is the frequency of the repair? 5) What has been your subjective experience with the performance of repair? (Does it work as you would expect? Does its overhead have a significant impact on the performance of your cluster?) Thanks! =Rob