somehow after a reboot of my aws datastax 2.1 instance i found that it upgraded cassandra from 1.0.7 to 1.1.1.
how do i replace this node? it seem like the ami is only for setting up clusters and not for adding single nodes?
thanks,
deno
aws ami
(5 posts) (3 voices)- Started 11 months ago by denov
- Latest reply from joaquin
- This topic is not resolved
-
Hello,
This shouldn't have happened due to this line that ensures new versions will never been installed:
https://github.com/riptano/ComboAMI/blob/2.2/ds2_configure.py#L743To remove the node, simple run a
nodetool decommissionon the node. If this fails, you can kill the node and run anodetool removetokenthat will remove the entire token and any data that may be on the node, so use cautiously.For the full documentation on how to expand an AMI cluster, see:
http://www.datastax.com/docs/1.1/install/expand_amiBut do note that you will have to set the
--releaseswitch appropriately:
https://github.com/riptano/ComboAMI/blob/2.2/SWITCHES.mdThanks,
JoaquinPosted 11 months ago # -
I received a forwarded email about your concerns between the 2.1 and 2.2 AMIs. Both AMI's are nearly identical and most of the changes were small edge cases and a complete rewrite for cleaner code. But both are compatible on a higher level.
Thanks,
JoaquinPosted 11 months ago # -
Hey Joaquin, what do you mean by "In the AWS Management Console, create a cluster with the number of nodes you want add, as described above."?
Create a new cluster with a different name from the running one? Stop all, and then reconfigure and join?
Wouldnt be better if we could supply our tokens when launching the new AMIs? Something like a manager or a URL to auto assign these?
Also, whats the purpose of reflector.php and tokentook?
Thank you
Posted 11 months ago # -
Hello pnegri,
You would ideally want to launch a new cluster with the same number of nodes that you are planning on adding.
Yes, you would want to merely modify all the tokens, seed ips, and set auto_bootstrap to true. Stop the service, clear the data at /raid0/cassandra/*, then start each node with 2 minutes in between, along with anything else I may be missing from the docs.
I used to have this option, but we deprecated it due to an expanding QA rubric. However, the typical use case for the AMI is something of a more easy, friendly, well-configured developer tool. Once you get to expanding a cluster, that's more of an "advanced" scope than what the AMI was meant to handle.
The expanding is also simple enough to where most cases are fairly straight forward. However, the edge cases where you're adding a new datacenter would be a bit tougher to code without some sort of manual intervention either way.
Reflector.php's description can be found here:
https://github.com/riptano/ComboAMI/blob/2.2/FILES.md#reflectorphpTokentool is a script that provides the computation for the tokens when the cluster boots up.
Cheers,
JoaquinPosted 11 months ago #
Reply
You must log in to post.