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 5B41B200BC7 for ; Fri, 25 Nov 2016 11:35:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 59D26160B01; Fri, 25 Nov 2016 10:35:49 +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 A3415160AF6 for ; Fri, 25 Nov 2016 11:35:48 +0100 (CET) Received: (qmail 32548 invoked by uid 500); 25 Nov 2016 10:35:46 -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 32534 invoked by uid 99); 25 Nov 2016 10:35:46 -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, 25 Nov 2016 10:35:46 +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 04D14C0339 for ; Fri, 25 Nov 2016 10:35:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3 X-Spam-Level: X-Spam-Status: No, score=-3 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6UvkkHeU1Q80 for ; Fri, 25 Nov 2016 10:35:43 +0000 (UTC) Received: from vhex.net (vhex.net [146.185.136.158]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3EF8D5FD0B for ; Fri, 25 Nov 2016 10:35:31 +0000 (UTC) Subject: Re: repair -pr in crontab To: user@cassandra.apache.org References: <22d40d80-67cf-a3af-a3d8-2585db798f61@vhex.net> <201611251430507792868@zjqunshuo.com> From: Artur Siekielski Message-ID: Date: Fri, 25 Nov 2016 11:34:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <201611251430507792868@zjqunshuo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit archived-at: Fri, 25 Nov 2016 10:35:49 -0000 Hi, yes, I read about how the repairing works, but the docs/blog posts lack practical recommendations and "best practices". For example, I found people having issues with running "repair -pr" simultaneously on all nodes, but it isn't clear it shouldn't be allowed. In the end I implemented rolling, sequential "repair -pr" run on all nodes (it's pretty easy to implement when you have Salt/Ansible, or even ssh). On 11/25/2016 07:30 AM, wxn002@zjqunshuo.com wrote: > Hi Artur, > When I asked similar questions, someone addressed me to the below links > and they are helpful. > > See http://www.datastax.com/dev/blog/repair-in-cassandra > https://lostechies.com/ryansvihla/2015/09/25/cassandras-repair-should-be-called-required-maintenance/ > https://cassandra-zone.com/understanding-repairs/ > > Cheers, > -Simon >