From user-return-33247-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Apr 5 17:05:00 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 66435F182 for ; Fri, 5 Apr 2013 17:05:00 +0000 (UTC) Received: (qmail 39780 invoked by uid 500); 5 Apr 2013 17:04:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 39742 invoked by uid 500); 5 Apr 2013 17:04: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 39730 invoked by uid 99); 5 Apr 2013 17:04:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Apr 2013 17:04:57 +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: local policy) Received: from [208.113.200.5] (HELO homiemail-a80.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Apr 2013 17:04:53 +0000 Received: from homiemail-a80.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTP id F38E437A076 for ; Fri, 5 Apr 2013 10:04:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=n9F7MGVyC3W+vM0rbhCbv8j2EJ o=; b=zyiwzFX5pL6un5fV/Rp609LBgR5XIOGo+eyjkvCT5iPEeRezP7krzXvM6m YI6N+GvQWvPC5RI+mGSmn4IIq2Wqh50PtoSw3aDX455ZFdwWIF6Sl7SPI9HuKlJW gwxJuGde/Wa5gPS4HKLIgBCHkOvTul88jeCoK/QYfFGsdJSUM= Received: from [10.65.15.205] (unknown [59.164.97.108]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTPSA id 630C537A065 for ; Fri, 5 Apr 2013 10:04:31 -0700 (PDT) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_29A85095-DA9C-4866-BC54-1B861F45CF6C" Message-Id: <35D894C4-F866-4CE5-853E-36CE18FA71BF@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: upgrading 1.1.x to 1.2.x via sstableloader Date: Fri, 5 Apr 2013 22:34:28 +0530 References: <652143E9-EA0C-441F-A57D-89452321EC32@thelastpickle.com> To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_29A85095-DA9C-4866-BC54-1B861F45CF6C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-2 > Is it safe to change sstable file name to avoid name collisions? Yes.=20 Make sure to change the generation number for all the components.=20 Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 4/04/2013, at 3:01 PM, Micha=B3 Czerwi=F1ski = wrote: > I see, thanks for the replay! >=20 > One more question: >=20 > I can see that multiple nodes have same sstable names for a certain = keyspace / cf. > I am moving 8 nodes to a 6 nodes cluster, so at some point when = putting sstables in place I would overwrite files from other node. What = is the best way to solve this problem? Is it safe to change sstable file = name to avoid name collisions? >=20 >=20 >=20 > On 4 April 2013 02:54, aaron morton wrote: > > java.lang.UnsupportedOperationException: SSTable = zzz/xxx/yyy-hf-47-Data.db is not compatible with current version ib > You cannot stream files that have a different on disk format. >=20 > 1.2 can read the old files, but cannot accept them as streams. You can = copy the files to the new machines and use nodetool refresh to load = them, then upgradesstables to re-write them before running repair. >=20 > Cheers >=20 > ----------------- > Aaron Morton > Freelance Cassandra Consultant > New Zealand >=20 > @aaronmorton > http://www.thelastpickle.com >=20 > On 3/04/2013, at 10:53 PM, Micha=B3 Czerwi=F1ski = wrote: >=20 > > Does anyone knows what is the best process to put data from = cassandra 1.1.x (1.1.7 to be more precise) to cassandra 1.2.3 ? > > > > I am trying to use sstableloader and stream data to a new cluster = but I get. > > > > ERROR [Thread-125] 2013-04-03 16:37:27,330 = IncomingTcpConnection.java (line 183) Received stream using protocol = version 5 (my version 6). Terminating connection > > > > ERROR [Thread-141] 2013-04-03 16:38:05,704 CassandraDaemon.java = (line 164) Exception in thread Thread[Thread-141,5,main] > > > > java.lang.UnsupportedOperationException: SSTable = zzz/xxx/yyy-hf-47-Data.db is not compatible with current version ib > > > > at = org.apache.cassandra.streaming.StreamIn.getContextMapping(StreamIn.java:77= ) > > > > at = org.apache.cassandra.streaming.IncomingStreamReader.(IncomingStreamR= eader.java:87) > > > > at = org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnectio= n.java:238) > > > > at = org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpCon= nection.java:178) > > > > at = org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.j= ava:78) > > > > > > > > I've changed Murmur3Partitioner to RandomPartitioner already and = I've noticed I am not able to use 1.1.7's sstableloader so I copied = sstables to new nodes and tried doing it locally on cassandra 1.2.3, but = it seems protocol versions do not match (see error above) > > > > The reason why I want to use sstableloader is that I have different = number of nodes and would like to avoid using rsync and then = repair/cleanup of excessive data. > > > > Thanks! > > >=20 >=20 --Apple-Mail=_29A85095-DA9C-4866-BC54-1B861F45CF6C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-2
 Is it safe to change = sstable file name to avoid name = collisions?
Yes. 
Make sure to change the = generation number for all the = components. 

Cheers

http://www.thelastpickle.com

On 4/04/2013, at 3:01 PM, Micha=B3 Czerwi=F1ski <michal@qubitproducts.com> = wrote:

I see, thanks for the = replay!

One more question:

I can see that multiple nodes have = same sstable names for a certain keyspace / cf.
I = am moving 8 nodes to a 6 nodes cluster, so at some point when putting = sstables in place I would overwrite files from other node. What is the = best way to solve this problem? Is it safe to change sstable file name = to avoid name collisions?



On 4 April 2013 = 02:54, aaron morton <aaron@thelastpickle.com> wrote:
> = java.lang.UnsupportedOperationException: SSTable = zzz/xxx/yyy-hf-47-Data.db is not compatible with current version ib
You cannot stream files that have a different on disk format.

1.2 can read the old files, but cannot accept them as streams. You can = copy the files to the new machines and use nodetool refresh to load = them, then upgradesstables to re-write them before running repair.

Cheers

-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 3/04/2013, at 10:53 PM, Micha=B3 Czerwi=F1ski <michal@qubitproducts.com> = wrote:

> Does anyone knows what is the best process to put data from = cassandra 1.1.x (1.1.7 to be more precise) to cassandra 1.2.3 ?
>
> I am trying to use sstableloader and stream data to a new cluster = but I get.
>
> ERROR [Thread-125] 2013-04-03 16:37:27,330 = IncomingTcpConnection.java (line 183) Received stream using protocol = version 5 (my version 6). Terminating connection
>
> ERROR [Thread-141] 2013-04-03 16:38:05,704 CassandraDaemon.java = (line 164) Exception in thread Thread[Thread-141,5,main]
>
> java.lang.UnsupportedOperationException: SSTable = zzz/xxx/yyy-hf-47-Data.db is not compatible with current version ib
>
>         at = org.apache.cassandra.streaming.StreamIn.getContextMapping(StreamIn.java:77= )
>
>         at = org.apache.cassandra.streaming.IncomingStreamReader.<init>(IncomingS= treamReader.java:87)
>
>         at = org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnectio= n.java:238)
>
>         at = org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpCon= nection.java:178)
>
>         at = org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.j= ava:78)
>
>
>
> I've changed Murmur3Partitioner to RandomPartitioner already and = I've noticed I am not able to use 1.1.7's sstableloader so I copied = sstables to new nodes and tried doing it locally on cassandra 1.2.3, but = it seems protocol versions do not match (see error above)
>
> The reason why I want to use sstableloader is that I have different = number of nodes and would like to avoid using rsync and then = repair/cleanup of excessive data.
>
> Thanks!
>



= --Apple-Mail=_29A85095-DA9C-4866-BC54-1B861F45CF6C--