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 37A2E103F8 for ; Mon, 23 Dec 2013 15:01:30 +0000 (UTC) Received: (qmail 1120 invoked by uid 500); 23 Dec 2013 15:01:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1065 invoked by uid 500); 23 Dec 2013 15:01:13 -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 973 invoked by uid 99); 23 Dec 2013 15:01:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Dec 2013 15:01:05 +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 (athena.apache.org: domain of rmenon@apigee.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Dec 2013 15:00:59 +0000 Received: by mail-ie0-f182.google.com with SMTP id as1so5990520iec.13 for ; Mon, 23 Dec 2013 07:00:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=U6/qXa52B7R4uN25OjkrgZEw1+9eCoARlsvG6xy/hW8=; b=OxFR4rY2cN/ZxEBg2LJAAE1rZGFiE2T7/HP+WdkomxKeSe2LsJleS6tcLnglcP0JMK +La5llBb9ckeUUReL1V3vNjTVB7ljeGUfdDkwPV/7YsriTbhnjRMBah9OBz+tBKW1R+B qCDNPhIuZbnzwB/M4ecSY71WqJhLJZQ6C1WAZAMHb8023LVYWbCtlWuVUwNprxxwgkA7 3ds+GVlP4LGXdYGKNamJb8cx4cMl1NPDhbKNeOf7G+7KeW3MC92ial2MP2U2Iffc2kCF VvTe8ycUX2EwG3P8pFSkiE6C5PYxiRw90DEaVHHarem72cgqRg4hvyS5+U5Xwl6aRzb/ IGnA== X-Gm-Message-State: ALoCoQnUdCvohk7lEMjfKyx4zVbsyetkl6X/K2mhHHFu2b/+RvtakGJzKNHqJLnZ7ITfdwmK8rtA X-Received: by 10.42.4.201 with SMTP id 9mr1796738ict.57.1387810839031; Mon, 23 Dec 2013 07:00:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.179.9 with HTTP; Mon, 23 Dec 2013 06:59:26 -0800 (PST) In-Reply-To: References: From: Rahul Menon Date: Mon, 23 Dec 2013 20:29:26 +0530 Message-ID: Subject: Re: Offline migration: Random->Murmur To: user Content-Type: multipart/alternative; boundary=001a11346bd213954f04ee34e4de X-Virus-Checked: Checked by ClamAV on apache.org --001a11346bd213954f04ee34e4de Content-Type: text/plain; charset=ISO-8859-1 Christian, I have been planning to migrate my cluster from random to murmur3 in a similar manner. I intend to use pycassa to read and then write to the newer cluster. My only concern would be ensuring the consistency of already migrated data as the cluster ( with random ) would be constantly serving the production traffic. I was able to do this on a non prod cluster, but production is a different game. I would also like to hear more about this, especially if someone was able to successfully do this. Thanks Rahul On Mon, Dec 23, 2013 at 6:45 PM, horschi wrote: > Hi list, > > has anyone ever tried to migrate a cluster from Random to Murmur? > > We would like to do so, to have a more standardized setup. I wrote a small > (yet untested) utility, which should be able to read SSTable files from > disk and write them into a cassandra cluster using Hector. This migration > would be offline of course and would only work for smaller clusters. > > Any thoughts on the topic? > > kind regards, > Christian > > PS: The reason for doing so are not "performance". It is to simplify > operational stuff for the years to come. :-) > --001a11346bd213954f04ee34e4de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Christian,

I have be= en planning to migrate my cluster from random to murmur3 in a similar manne= r. I intend to use pycassa to read and then write to the newer cluster. My = only concern would be ensuring the consistency of already migrated data as = the cluster ( with random ) would be constantly serving the production traf= fic. I was able to do this on a non prod cluster, but production is a diffe= rent game.

I would also like to hear more about this, especially= if someone was able to successfully do this.

Thanks
Rahul


On Mon, Dec 23, 2013 at 6:45 PM, horsc= hi <horschi@gmail.com> wrote:
Hi= list,

has anyone ever tried to migrate a cluster from Random = to Murmur?

We would like to do so, to have a more standardized setup. I wrot= e a small (yet untested) utility, which should be able to read SSTable file= s from disk and write them into a cassandra cluster using Hector. This migr= ation would be offline of course and would only work for smaller clusters.<= br>

Any thoughts on the topic?

kind regards,<= br>Christian

PS: The reason for doing so are not "perform= ance". It is to simplify operational stuff for the years to come. :-)<= br>

--001a11346bd213954f04ee34e4de--