From user-return-37157-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Oct 18 18:40:33 2013 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 281C810803 for ; Fri, 18 Oct 2013 18:40:33 +0000 (UTC) Received: (qmail 7420 invoked by uid 500); 18 Oct 2013 18:40:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7386 invoked by uid 500); 18 Oct 2013 18:40:19 -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 7371 invoked by uid 99); 18 Oct 2013 18:40:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 18:40:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of abarua@247-inc.com designates 213.199.154.77 as permitted sender) Received: from [213.199.154.77] (HELO emea01-db3-obe.outbound.protection.outlook.com) (213.199.154.77) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 18:40:10 +0000 Received: from SIXPR03MB157.apcprd03.prod.outlook.com (10.242.62.142) by SIXPR03MB158.apcprd03.prod.outlook.com (10.242.62.146) with Microsoft SMTP Server (TLS) id 15.0.800.7; Fri, 18 Oct 2013 18:39:44 +0000 Received: from SIXPR03MB157.apcprd03.prod.outlook.com ([169.254.15.176]) by SIXPR03MB157.apcprd03.prod.outlook.com ([169.254.15.176]) with mapi id 15.00.0800.005; Fri, 18 Oct 2013 18:39:43 +0000 From: Arindam Barua To: "user@cassandra.apache.org" Subject: upgrading Cassandra server hardware best practice? Thread-Topic: upgrading Cassandra server hardware best practice? Thread-Index: Ac7MMUiQg2CzhX04Rf6pkGwTYCKjmA== Date: Fri, 18 Oct 2013 18:39:42 +0000 Message-ID: <74b9e7531c234a9e9c0e942a1dcb82fa@SIXPR03MB157.apcprd03.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [98.207.232.166] x-forefront-prvs: 00032065B2 x-forefront-antispam-report: SFV:NSPM;SFS:(199002)(189002)(164054003)(51856001)(77096001)(76786001)(74876001)(15202345003)(81816001)(4396001)(33646001)(85306002)(16236675002)(83322001)(81542001)(69226001)(65816001)(63696002)(81342001)(74706001)(46102001)(56776001)(54316002)(76176001)(15975445006)(53806001)(77982001)(59766001)(76796001)(76576001)(54356001)(74366001)(79102001)(56816003)(80976001)(19300405004)(50986001)(49866001)(47736001)(31966008)(74662001)(66066001)(47446002)(19609705001)(74316001)(47976001)(83072001)(19580395003)(81686001)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:SIXPR03MB158;H:SIXPR03MB157.apcprd03.prod.outlook.com;CLIP:98.207.232.166;FPR:;RD:InfoNoRecords;A:1;MX:1;LANG:en; Content-Type: multipart/alternative; boundary="_000_74b9e7531c234a9e9c0e942a1dcb82faSIXPR03MB157apcprd03pro_" MIME-Version: 1.0 X-OriginatorOrg: 247-inc.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_74b9e7531c234a9e9c0e942a1dcb82faSIXPR03MB157apcprd03pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We currently have 2 datacenters and a ring of 5 Cassandra servers on each d= atacenter. We are getting new hardware, and after evaluating them, plan to = upgrade the ring to the new hardware. Is there any recommended procedure for doing so? This is one of the options= we are considering: 1. Add new hardware servers to cluster a. To calculate the initial_token for the new cluster, assume that yo= u will only have the new server ring. b. If there is no clash of token with existing ring, assign the new se= rvers those tokens. Otherwise increment the clashing tokens by 1, and assig= n it to the new servers. c. Add the servers one by one. 2. Remove old servers a. Remove the servers one by one by doing "nodetool decommission". Or, is some other strategy, like adding a new server, and then removing an = old server a better option? Also, does anyone have any experience running a cluster with heterogeneous = hardware. Old Hardware: 2 quad core processors, 32 GB RAM, four 1-TB disks New Hardware: 2 8-core processors, 128 GB RAM, eight 1-TB disks Cassandra version: 1.1.5. Thanks, Arindam --_000_74b9e7531c234a9e9c0e942a1dcb82faSIXPR03MB157apcprd03pro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

We currently have 2 datacenters and a ring of 5 Cass= andra servers on each datacenter. We are getting new hardware, and after ev= aluating them, plan to upgrade the ring to the new hardware.

 

Is there any recommended procedure for doing so? Thi= s is one of the options we are considering:

 

1.       Add new hardware servers to cluster

a.       To calculate the initial_token for the new cluster,= assume that you will only have the new server ring.

b.      If there is no clash of token with existing ring, a= ssign the new servers those tokens. Otherwise increment the clashing tokens= by 1, and assign it to the new servers.

c.       Add the servers one by one.

2.       Remove old servers

a.       Remove the servers one by one by doing “nodet= ool decommission”.

Or, is some other strategy, like adding a new server= , and then removing an old server a better option?

 

Also, does anyone have any experience running a clus= ter with heterogeneous hardware.

 

Old Hardware: 2 quad core processors, 32 GB RAM, fou= r 1-TB disks

New Hardware: 2 8-core processors, 128 GB RAM, eight= 1-TB disks

 

Cassandra version: 1.1.5.

 

Thanks,

Arindam

 

--_000_74b9e7531c234a9e9c0e942a1dcb82faSIXPR03MB157apcprd03pro_--