The tokens were different than the production cluster and after closer
inspection a lot of data wasn't queryable (as excpected I suppose). I set
the tokens and everything seems ok now.
Auto bootstrap was false so no issues there.
Thanks for the insight Shyamal! It's good to finally have this up
> "Eric" == Eric Czech writes:
Eric> Yea that's not a mapping I'd like to maintain either -- as an
Eric> experiment, I copied production sstables to the analysis
Eric> cluster and ran brisk/cassandra without specifying an initial
Eric> token (after deleting the LocationInfo* f
Yea that's not a mapping I'd like to maintain either -- as an experiment, I
copied production sstables to the analysis cluster and ran brisk/cassandra
without specifying an initial token (after deleting the LocationInfo* files
and renaming the cluster). As far as I can tell, everything is running
Another thing Edward if you don't mind, how does cassandra choose a node to
associate with a token if there is more than one node with the same token?
I know that's definitely not a favorable situation to be in, but I'm
curious how my production ring chose to switch ownership of the tokens.
On Su
> "Eric" == Eric Czech writes:
Eric> Hi Shyamal, I was using the same cluster name but since
Eric> writing that first email, I've already had success bringing up
Eric> nodes in the analysis cluster with a different cluster name
Eric> after deleting the LocationInfo* tables.
Hi Shyamal,
I was using the same cluster name but since writing that first email, I've
already had success bringing up nodes in the analysis cluster with a
different cluster name after deleting the LocationInfo* tables.
How have you been setting the tokens in the copied version of the cluster?
A
> "Eric" == Eric Czech writes:
Eric> We're exploring a data processing procedure where we snapshot
Eric> our production cluster data and move that data to a new
Eric> cluster for analysis but I'm having some strange issues where
Eric> the analysis cluster is still somehow awar
Thanks Edward. So would you say this is a good strategy:
1. snapshot files from production cluster
2. move snapshot files to analysis cluster in a one-to-one node fashion
(the system/LocationInfo* sstables could be excluded here but I'm moving
them all because the transfer is also part of our D
On Sun, Oct 2, 2011 at 4:25 PM, Eric Czech wrote:
> We're exploring a data processing procedure where we snapshot our
> production cluster data and move that data to a new cluster for analysis but
> I'm having some strange issues where the analysis cluster is still somehow
> aware of the producti
We're exploring a data processing procedure where we snapshot our production
cluster data and move that data to a new cluster for analysis but I'm having
some strange issues where the analysis cluster is still somehow aware of the
production cluster (i.e. the production cluster ring is trying to in
10 matches
Mail list logo
