Thank you Riccardo Murri
1. Load balancing: You submit the number of jobs to the cluster and
depending upon the number of jobs, cluster adds or removes the nodes. This
is automatic and is accomplished by running load balancer in parallel. In
this way, users can go on submitting the jobs to the head/master node and
there is no need to manually add/remove nodes.
2. I tried again with prebuilt AMI (by building it again) and it is working
now. I think there was some issues with earlier AMI. Thank you for
alternate playbook technique.
On Sunday, April 15, 2018 at 3:54:53 AM UTC-4, Riccardo Murri wrote:
> > First of all thank you very much for such a wonderful software.
> Glad you like it! And thanks for getting back with questions -- this
> is how a community is built and grows :-)
> > 1. Is there any way already implemented for load balancing in
> I'm not sure what you mean by "load balancing" here -- can you please
> describe the feature you would like in a bit more detail?
> > 2. Is there way to install or use some pre- or post scripts to install
> > configure softwares on the cluster? I want to install some softwares on
> > default AMI and mount EFS mount to it for use.
> There are basically two ways of doing this:
> a. Prepare additional Ansible playbooks to run alongside
> ElastiCluster's own ones. You can run the additional playbooks in two
> * either specify them as additional arguments to `elasticluster setup`,
> elasticluster setup my-cluster -- /path/to/my/playbook.yml
> This will run `playbook.yml` through Ansible *after* other
> ElastiCluster playbooks have run, so you can do post-install actions.
> * or install from source and override the `before.yml` and `after.yml`
> playbooks in the `elasticluster/share/playbooks` directory.
> b. Use a VM snapshot as a starting point so you can customize it to
> your liking. (This is the approach you seem to have already taken, see
> below for additional comments.)
> > I had preconfigured AMI with EFS mount on /etc/fstab with some
> > softwares but launching it with Elasticluster is giving some problems.
> > there any specific way that AMI should be built?
> This would be approach b. above, and it is certainly meant to be
> It's hard to say why it isn't working for you without additional details:
> what playbook / cluster setup are you running? what error(s) are you
> Hope this helps!
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.