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 5D2C2D518 for ; Mon, 27 Aug 2012 23:53:23 +0000 (UTC) Received: (qmail 33763 invoked by uid 500); 27 Aug 2012 23:53:21 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 33739 invoked by uid 500); 27 Aug 2012 23:53:21 -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 33731 invoked by uid 99); 27 Aug 2012 23:53:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 23:53:20 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Edward.Sargisson@globalrelay.net designates 208.81.212.160 as permitted sender) Received: from [208.81.212.160] (HELO ex1.globalrelay.net) (208.81.212.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 23:53:13 +0000 Received: from [10.5.5.212] (208.81.212.224) by ex1.office.globalrelay.net (10.6.60.10) with Microsoft SMTP Server id 8.1.436.0; Mon, 27 Aug 2012 16:52:51 -0700 Message-ID: <503C0853.2080505@globalrelay.net> Date: Mon, 27 Aug 2012 16:52:51 -0700 From: Edward Sargisson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: "user@cassandra.apache.org" Subject: Automating nodetool repair Content-Type: multipart/alternative; boundary="------------010105040804020105090109" --------------010105040804020105090109 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Hi all, So nodetool repair has to be run regularly on all nodes. Does anybody have any interesting strategies or tools for doing this or is everybody just setting up cron to do it? For example, one could write some Puppet code to splay the cron times around so that only one should be running at once. Or, perhaps, a central orchestrator that is given some known quiet time and works its way through the list, running nodetool repair one at a time (using RPC?) until it runs out of time. Cheers, Edward -- Edward Sargisson senior java developer Global Relay edward.sargisson@globalrelay.net *866.484.6630* New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore (+65.3158.1301) Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more. Ask about *Global Relay Message* *--- *The Future of Collaboration in the Financial Services World * *All email sent to or from this address will be retained by Global Relay's email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Global Relay will not be liable for any compliance or technical information provided herein. All trademarks are the property of their respective owners. --------------010105040804020105090109 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Hi all,
So nodetool repair has to be run regularly on all nodes. Does anybody have any interesting strategies or tools for doing this or is everybody just setting up cron to do it?

For example, one could write some Puppet code to splay the cron times around so that only one should be running at once.
Or, perhaps, a central orchestrator that is given some known quiet time and works its way through the list, running nodetool repair one at a time (using RPC?) until it runs out of time.

Cheers,
Edward

Edward Sargisson

senior java developer
Global Relay

edward.sargisson@globalrelay.net

866.484.6630
New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore (+65.3158.1301)

Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more.

Ask about Global Relay Message — The Future of Collaboration in the Financial Services World

All email sent to or from this address will be retained by Global Relay’s email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Global Relay will not be liable for any compliance or technical information provided herein. All trademarks are the property of their respective owners.

--------------010105040804020105090109--