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 1E341D858 for ; Wed, 10 Oct 2012 16:46:45 +0000 (UTC) Received: (qmail 54021 invoked by uid 500); 10 Oct 2012 16:46:42 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 53957 invoked by uid 500); 10 Oct 2012 16:46:42 -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 53813 invoked by uid 99); 10 Oct 2012 16:46:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 16:46:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of btoddb@gmail.com designates 209.85.214.172 as permitted sender) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 16:46:36 +0000 Received: by mail-ob0-f172.google.com with SMTP id v19so884761obq.31 for ; Wed, 10 Oct 2012 09:46:15 -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:content-transfer-encoding; bh=6aYxmIWgbLj1n4ynjedI8nHdTj6hHWZISTKPBuOzblM=; b=UZVZh2kdBJdeICAv/IRIrVF94dhGaPszCOorxApf5X8BG/14RVIKB9DjstIC/82AlJ oahGDGy++cYB34LC2KDRxHRAW1REei1785lYXeE97Aiiut8Aay06op2lGCj0OQKKk8dH r3hvRUcTIvRsq7WKX2zgyWEMncLM4T1jqiVEhtw7IQED3TneHWmJPRQFEhRLtaXBS0bc txn110HQIipRsqOUh2f0KD5iIn1fBty9mVTdcQPrxNccbtkj6uIhwtjNWQFsD5lzdez8 +Y3Q8rakwOWYaZ5pWsjbkviKyR9EIyFLutIvX57VYNqBAl5luJ3HxRlj3COIiwLX1poI NXqQ== MIME-Version: 1.0 Received: by 10.60.170.176 with SMTP id an16mr19142426oec.57.1349887575518; Wed, 10 Oct 2012 09:46:15 -0700 (PDT) Received: by 10.182.171.8 with HTTP; Wed, 10 Oct 2012 09:46:15 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Oct 2012 09:46:15 -0700 Message-ID: Subject: Re: Upgrading hardware on a node in a cluster From: "B. Todd Burruss" To: user@cassandra.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable if you have N nodes in your cluster, add N new nodes using the new hardware, then decommision the old N nodes. (and migrate to VPC like dean said) On Wed, Oct 10, 2012 at 5:23 AM, Hiller, Dean wrote: > Well, you could use amazon VPC in which case you DO pick the IP yourself = ;)=85.it makes life a bit easier. > > Dean > > From: Martin Koch > > Reply-To: "user@cassandra.apache.org" <= user@cassandra.apache.org> > Date: Wednesday, October 10, 2012 3:29 AM > To: "user@cassandra.apache.org" > > Subject: Upgrading hardware on a node in a cluster > > Hi List > > I'd like to migrate my nodes in a cluster to new hardware, moving one nod= e at a time. > > I'm running the cluster in Amazon, so I don't get to pick the ip number o= f each host myself. > > I'd like to decommision, say, the node with token 0, and bring that node = up on the new hardware (which will have a new IP number). > > Can anyone provide me with a recipe for doing this? I've looked around an= d read about nodetool move, which didn't make me much wiser. > > Thanks for your help, > /Martin Koch - Issuu - Senior Systems Architect