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 649ED100CC for ; Mon, 7 Apr 2014 16:26:01 +0000 (UTC) Received: (qmail 16189 invoked by uid 500); 7 Apr 2014 16:25:58 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 15818 invoked by uid 500); 7 Apr 2014 16:25:57 -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 15805 invoked by uid 99); 7 Apr 2014 16:25:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2014 16:25:55 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bm3780@gmail.com designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yh0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Apr 2014 16:25:50 +0000 Received: by mail-yh0-f45.google.com with SMTP id a41so6052031yho.18 for ; Mon, 07 Apr 2014 09:25:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=/xBi1Hb0SujHfaQf9LuFVMVEnnoUDVSW/t5ctkkE0AU=; b=P4LLG6tGSLpxJ7LOz1AlcMzSrlaRJ0l1jr+1K8nkhTm4KGaOaBc/IdF2r0SZ9UhdYb TxmQ0WuSE+8o4cIO9buX2G/j5UEfmrgbaJfHJ2s7AkRIfy1NTKeHUxpcLO9w3RmKsy14 0PDIaQFYB0oF5rQx4w+nWQcPvZgnGt5W4wemHAlOiixxHgM7/XawHPBDqAss3VCOfGm9 BCWapYsklsM4WAFDoKAu0LEw9BxgzqwDFMdnSW3LPGDXIpJ///bcp5Hv4zExA3Bq1uDR k/w3L58AtAk8mOCnAxesSGMWjYimbU7v+Y7dct8SLKplf4b+b8JS0scNqPldJz1xQwKq M48A== MIME-Version: 1.0 X-Received: by 10.236.42.43 with SMTP id i31mr46615529yhb.31.1396887928745; Mon, 07 Apr 2014 09:25:28 -0700 (PDT) Received: by 10.170.216.213 with HTTP; Mon, 7 Apr 2014 09:25:28 -0700 (PDT) Date: Mon, 7 Apr 2014 12:25:28 -0400 Message-ID: Subject: Migrating to new datacenter From: Brandon McCauslin To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3010e5b1c8b3d204f6765030 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3010e5b1c8b3d204f6765030 Content-Type: text/plain; charset=ISO-8859-1 We're currently running a small 5 node 2.0.5 cluster in a single datacenter using the SimpleStrategy replication strategy with replication factor of 3. We want to migrate our data from our current datacenter to a new datacenter, without incurring any downtime or data loss. There is no plan to maintain or keep the old (current) datacenter after the migration is complete. I'm wondering how best to go about this migration. *Shoud We:* 1. add a 2nd datacenter as described here - "Adding a datacenter to cluster", then decommission the 1st datacenter. Can we even do this given we're currently setup with SimpleStrategy replication? 2. or should we just start adding new nodes from the new datacenter to our existing cluster as described here? Then once we've added all the new nodes, start decommissioning all the old nodes from the old/current datacenter as described here . Thanks for your help and time! --20cf3010e5b1c8b3d204f6765030 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We're currently running a small 5 node 2.0.5 clus= ter in a single datacenter using the SimpleStrategy replication strategy wi= th replication factor of 3. =A0We want to migrate our data from our current= datacenter to a new datacenter, without incurring any downtime or data los= s. =A0There is no plan to maintain or keep the old (current) datacenter aft= er the migration is complete. =A0I'm wondering how best to go about thi= s migration.

Shoud We:
  1. add a 2nd dat= acenter as described here - "Ad= ding a datacenter to cluster", then=A0decommission the 1st datacenter. =A0Can we even do this given w= e're currently setup with SimpleStrategy replication?
  2. or should we just start adding new nodes from the new datacenter to our= existing cluster as described=A0h= ere? =A0Then once we've added all the new nodes, start decommission= ing all the old nodes from the old/current datacenter as described=A0here.
Thanks for your help and time!
--20cf3010e5b1c8b3d204f6765030--