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 6806C11C6B for ; Thu, 31 Jul 2014 15:16:41 +0000 (UTC) Received: (qmail 23194 invoked by uid 500); 31 Jul 2014 15:16:35 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 23158 invoked by uid 500); 31 Jul 2014 15:16:35 -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 23148 invoked by uid 99); 31 Jul 2014 15:16:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 15:16:35 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.149.113.243] (HELO tcmail23.telekom.de) (80.149.113.243) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jul 2014 15:16:34 +0000 Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail21.telekom.de with ESMTP; 31 Jul 2014 17:16:08 +0200 X-IronPort-AV: E=Sophos;i="5.01,772,1400018400"; d="scan'208";a="633259911" Received: from he111527.emea1.cds.t-internal.com ([10.125.90.86]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 31 Jul 2014 17:16:08 +0200 Received: from HE100018.emea1.cds.t-internal.com (10.125.65.199) by HE111527.EMEA1.CDS.T-INTERNAL.COM (10.125.90.86) with Microsoft SMTP Server (TLS) id 8.3.348.2; Thu, 31 Jul 2014 17:16:08 +0200 Received: from HE113566.emea1.cds.t-internal.com ([10.125.65.112]) by HE100018.emea1.cds.t-internal.com ([2002:769:410b::769:410b]) with mapi; Thu, 31 Jul 2014 17:16:07 +0200 From: To: Date: Thu, 31 Jul 2014 17:16:07 +0200 Subject: AW: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed partitioner settings Thread-Topic: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed partitioner settings Thread-Index: Ac+so4vXQzrtqnKGQye3pPj8l8Vt3AALPpzA Message-ID: <4DE64738F836F946B079ECB746E63B4BEC1895D5D1@HE113566.emea1.cds.t-internal.com> References: <1406637000080-7596019.post@n2.nabble.com> <1406638432277-7596021.post@n2.nabble.com> <1406789699537-7596062.post@n2.nabble.com> <1AFAEF95-D202-45DC-B7AB-E1D25EFFA9D4@rahul.be> In-Reply-To: <1AFAEF95-D202-45DC-B7AB-E1D25EFFA9D4@rahul.be> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Well, we ran StorageService.bulkLoad via JMX. According to http://www.datastax.com/dev/blog/bulk-loading this should hav= e the same effect and can be done on the same machine: "Because the sstableloader uses gossip to communicate with other nodes, if = launched on the same machine that a given Cassandra node, it will need to u= se a different network interface than the Cassandra node. But if you want t= o load data from a Cassandra node, there is a simpler solution: you can use= the JMX->StorageService->bulkload() call from said node." -----Urspr=FCngliche Nachricht----- Von: Rahul Neelakantan [mailto:rahul@rahul.be]=20 Gesendet: Donnerstag, 31. Juli 2014 11:40 An: user@cassandra.apache.org Cc: cassandra-user@incubator.apache.org Betreff: Re: Migration from Cassandra 1.2.5 to Cassandra 2.0.8 with changed= partitioner settings You said you tried restoring a snapshot via bulk loader, did you actually r= un sstableloader? Rahul Neelakantan > On Jul 31, 2014, at 2:54 AM, tsi wrote: >=20 > Well, the new Cassandra cluster is already setup with the different=20 > partitioner settings and there are already other applications running on = it. > So the task is to migrate our application data to this new cluster to=20 > avoid setting up a dedicated Cassandra cluster just for our application. >=20 >=20 >=20 > -- > View this message in context:=20 > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Migra > tion-from-Cassandra-1-2-5-to-Cassandra-2-0-8-with-changed-partitioner- > settings-tp7596019p7596062.html Sent from the=20 > cassandra-user@incubator.apache.org mailing list archive at Nabble.com.