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 CAF04118DF for ; Thu, 22 May 2014 20:32:52 +0000 (UTC) Received: (qmail 12157 invoked by uid 500); 22 May 2014 20:32:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 12121 invoked by uid 500); 22 May 2014 20:32:50 -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 12113 invoked by uid 99); 22 May 2014 20:32:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2014 20:32:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ajazam@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 May 2014 20:32:47 +0000 Received: by mail-la0-f45.google.com with SMTP id gl10so3147769lab.4 for ; Thu, 22 May 2014 13:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6N0fP9KIrdOCnvOEvNzm32QS++LRNFwOQX92WxYzvf0=; b=nwqyA9d2fjtPOYi47w2b0CfMGbDyt6RfYLkUv73fcBmLw3BVBraD5dY/9wCIuxPOPC 2cYWGGFBz1LW5D18xqJ/yAuZ71oarQc2AabzjCO29ApAF88Vh5B9m/rNoTQybISgmK6k MmePxTMe3nyX5yOr5kONdhvpFpGxnolpvURKxB61u+7IH5kPzZ4gL60U/NkrNY1iZF4a udZmd0aai9BD+GboMSX76OLLxgM0jfW0bFmcujt6p+S8IW6x03EL9EANrsnq/3qoNy4i i6BcVSvm3gIK7d6ad/5RuetIzhUWbc90l1b7pmEGChEUZIoVTHz4M4t+jgGch0l/22Kh OYFw== MIME-Version: 1.0 X-Received: by 10.112.151.229 with SMTP id ut5mr60240lbb.76.1400790743828; Thu, 22 May 2014 13:32:23 -0700 (PDT) Received: by 10.112.173.198 with HTTP; Thu, 22 May 2014 13:32:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 22 May 2014 21:32:23 +0100 Message-ID: Subject: Re: autoscaling cassandra cluster From: Jabbar Azam To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7bb70aa4b0ce3b04fa0302a4 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb70aa4b0ce3b04fa0302a4 Content-Type: text/plain; charset=UTF-8 Netflix uses Scryer http://techblog.netflix.com/2013/11/scryer-netflixs-predictive-auto-scaling.htmlfor predictive and reactive autoscaling but they only refer to EC2 instances. They don't mention anything about cassandra scaling or adding and removing nodes. I've just looked at the priam wiki and it also doesn't mention scaling. It also mentions that vnodes aren't fully supported. That's no use for me as I'm using 2.x. The other issue, rather feature of cassandra, is that adding a new node increases the load on the system so this surge would need to be taken into account. I think I'll leave this problem for more intelligent people than me and concentrate on the application logic, which can scale by adding or removing application and front end servers. Thanks for all your comments. Thanks Jabbar Azam On 22 May 2014 19:55, Robert Coli wrote: > On Wed, May 21, 2014 at 4:35 AM, Jabbar Azam wrote: > >> Has anybody got a cassandra cluster which autoscales depending on load or >> times of the day? >> > > Netflix probably does, managed with Priam. > > In general I personally do not consider Cassandra's mechanisms for joining > and parting nodes to currently work well enough to consider designing a > production system which would do so as part of regular operation. > > =Rob > > --047d7bb70aa4b0ce3b04fa0302a4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Netflix uses Scryer=C2=A0http://techblog= .netflix.com/2013/11/scryer-netflixs-predictive-auto-scaling.html for p= redictive and reactive autoscaling but they only refer to EC2 instances. Th= ey don't mention anything about cassandra scaling or adding and removin= g nodes.

I've just looked at the priam wiki and it also doesn'= ;t mention scaling. It also mentions that vnodes aren't fully supported= . That's no use for me as I'm using 2.x. The other issue, rather fe= ature of cassandra, is that adding a new node increases the load on the sys= tem so this surge would need to be taken into account.

I think I'll leave this problem for more intelligen= t people than me and concentrate on the application logic, which can scale = by adding or removing application and front end servers.

Thanks for all your comments.
--047d7bb70aa4b0ce3b04fa0302a4--