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 B053E177F5 for ; Thu, 23 Oct 2014 09:18:40 +0000 (UTC) Received: (qmail 89663 invoked by uid 500); 23 Oct 2014 09:18:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 89626 invoked by uid 500); 23 Oct 2014 09:18:38 -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 89616 invoked by uid 99); 23 Oct 2014 09:18:38 -0000 Received: from ec2-54-191-145-13.us-west-2.compute.amazonaws.com (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2014 09:18:38 +0000 Received: from mx1-us-west.apache.org (localhost [127.0.0.1]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id AC76626EE2 for ; Thu, 23 Oct 2014 09:18:37 +0000 (UTC) Received: by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org, from userid 114) id A1EC425DB8; Thu, 23 Oct 2014 09:18:37 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx1-us-west.apache.org X-Spam-Level: * X-Spam-Status: No, score=1.5 required=10.0 tests=HTML_MESSAGE, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=disabled version=3.4.0 Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 1133E26EE2 for ; Thu, 23 Oct 2014 09:18:36 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id hz20so476136lab.25 for ; Thu, 23 Oct 2014 02:18:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=8VZveHgv6Yv5yY2m/aQtxNQDeHNy3/79djRMSjtw6tg=; b=YdZOd60RVmIlUOLXFafM8tlp0KEkkPejIkCVM7gML8JOSDzWtqcG9kfZLRpI0ZEveQ RGitZn8sBw8FqoDqxRuXB/ldf2GXweimfQyibuh7g3AuoxorqAgEc2qR6sUsd26vqSD4 VGSPNrQGgOF/2tjJLGgANXAgXULbkUeerKwDheJg61P7i9LfSbbzMCfsIl38ZE4N+Lj9 8ibwEvkqh2JZxop1mn8xCT8y+1fwRfdpnP9TJHb9Cqi+kPMPJ+DvvjHzrn8kI6VY7nCF m/JmzVj+tora/8kx8MLNgQXaflA/kshbGxkIuDzUt39fmd0lpy4BjJeVZW6l9OAfpFYc 9jzQ== X-Received: by 10.112.132.34 with SMTP id or2mr3577116lbb.75.1414055908589; Thu, 23 Oct 2014 02:18:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.57.202 with HTTP; Thu, 23 Oct 2014 02:18:08 -0700 (PDT) From: Alain RODRIGUEZ Date: Thu, 23 Oct 2014 11:18:08 +0200 Message-ID: Subject: Operating on large cluster To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b3a82381fc7430506138cac X-Virus-Scanned: ClamAV using ClamSMTP --047d7b3a82381fc7430506138cac Content-Type: text/plain; charset=ISO-8859-1 Hi, I was wondering about how do you guys handle a large cluster (50+ machines). I mean there is sometime you need to change configuration (cassandra.yaml) or send a command to one, some or all nodes (cleanup, upgradesstables, setstramthoughput or whatever). So far we have been using things like custom scripts for repairs or any routine maintenance and cssh for specific and one shot actions on the cluster. But I guess this doesn't really scale, I guess we coul use pssh instead. For configuration changes we use Capistrano that might scale properly. So I would like to known, what are the methods that operators use on large cluster out there ? Have some of you built some open sourced "cluster management" interfaces or scripts that could make things easier while operating on large Cassandra clusters ? Alain --047d7b3a82381fc7430506138cac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I was wondering about how do you gu= ys handle a large cluster (50+ machines).

I mean t= here is sometime you need to change configuration (cassandra.yaml) or send = a command to one, some or all nodes (cleanup, upgradesstables, setstramthou= ghput or whatever).

So far we have been using thin= gs like custom scripts for repairs or any routine maintenance and cssh for = specific and one shot actions on the cluster. But I guess this doesn't = really scale, I guess we coul use pssh instead. For configuration changes w= e use Capistrano that might scale properly.

So I w= ould like to known, what are the methods that operators use on large cluste= r out there ? Have some of you built some open sourced "cluster manage= ment" interfaces or scripts that could make things easier while operat= ing on large Cassandra clusters ?

Alain
--047d7b3a82381fc7430506138cac--