Thanks a lot for your reply! So this helps a bit with my question in the previous post too then.
So to sum up: it is misleading that the output from the ansible task suggests you to rerun with the --limit option, as it can not be used with elasticluster? If a task fails and the cluster is not set up properly, and I do not want to remove the node, must I fix the ansible task, and then rerun the whole setup step again? With as you say elasticluster setup mycluster Or is the point of your suggestion above that it is better to remove the failed node, then fix the ansible scripts, then run setup again on the new cluster? Thanks! Maiken On Tuesday, April 2, 2019 at 12:30:07 PM UTC+2, Riccardo Murri wrote: > > Hello Maike, > > > How is this exactly supposed to be applied? > > It isn't. Ansible's `--limit` option will limit also the information > gathering to the listed hosts, thus breaking ElastiCluster's playbooks > which rely on a "global view" of the cluster (i.e., much of the info > is taken dynamically from discovered `hostvars` instead of filled in > statically in the inventory). > > You can use `--no-setup` if you want to run a batch of operations in > ElastiCluster and only reconfigure the cluster at the end:: > > elasticluster remove-node mycluster compute003 --no-setup > elasticluster remove-node mycluster compute004 --no-setup > elasticluster resize --add 2:bigcompute --no-setup mycluster > # now configure the cluster with the new "shape" > elasticluster setup mycluster > > Does this help? > > Ciao, > R > -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
