If a node is a seed node it will not bootstrap data from others the first time
it starts.
You can always run a nodetool repair when you think data is not where it should
be.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickl
More info.
I see this problem only if rest of cluster runs 1.1.5 and I try to replace
dead node by version 1.1.7 or higher. If I upgrade rest of cluster to the
same version (I tried 1.1.10) everything is ok. I guess there is some
incompatibility between 1.1.5 and 1.1.7 and higher.
Thank you,
And
I removed Priam and get the same picture.
What I do is- I added to cassandra-env.sh two lines and start cassandra.
JVM_OPTS="$JVM_OPTS
-Dcassandra.initial_token=aaba"
JVM_OPTS="$JVM_OPTS
-Dcassandra.replace_token=aaba"
Then I can successfu
You may have bumped to this issue:
https://github.com/Netflix/Priam/issues/161
make sure is_replace_token Priam API call is working for you.
On Fri, Mar 8, 2013 at 8:22 AM, aaron morton wrote:
> If it does not have the schema check the logs for errors and ensure it is
> actually part of the clust
If it does not have the schema check the logs for errors and ensure it is
actually part of the cluster.
You may have better luck with Priam specific questions on
https://github.com/Netflix/Priam
Cheers
-
Aaron Morton
Freelance Cassandra Developer
New Zealand
@aaronmorton
http
Hello everybody!
I used to run cassandra 1.1.5 with Priam. To replace dead node priam
launches cassandra with cassandra.replace_token property. It works smoothly
with 1.1.5. Couple days ago I moved to 1.1.10 and have a problem now. New
cassandra successfully starts, joins the ring but it doesn't s
