cular SSTable in the set
was corrupted?
Scott
From: aaron morton [aa...@thelastpickle.com]
Sent: Wednesday, January 18, 2012 1:52 AM
To: user@cassandra.apache.org
Subject: Re: JMX BulkLoad weirdness
I'd need the version number to be sure, but it looks like
o I suppose I'll ask again, is that error
> something to be concerned about?
>
> Thanks,
>
> Scott
> From: aaron morton [aa...@thelastpickle.com]
> Sent: Sunday, January 15, 2012 12:07 PM
> To: user@cassandra.apache.org
> Subject: Re: JMX BulkLoad weirdness
>
ed about?
Thanks,
Scott
From: aaron morton [aa...@thelastpickle.com]
Sent: Sunday, January 15, 2012 12:07 PM
To: user@cassandra.apache.org
Subject: Re: JMX BulkLoad weirdness
If you are doing a straight one-to-one copy from one cluster to another try…
1) nodetool s
If you are doing a straight one-to-one copy from one cluster to another try…
1) nodetool snapshot on each prod node for the system and application key
spaces.
2) rsync system and app key space snapshots
3) update the yaml files on the new cluster to have the correct initial_tokens.
This is not n
Hi all,
I'm trying to copy a column family from our production cluster to our
development one for testing purposes, so I thought I would try the bulkload
API. Since I'm lazy, I'm using the Cassandra bulkLoad JMX call from one of the
development machines. Here are the steps I followed:
1. (on p