Re: is mandatory that master instance is the same kind of instance than compute nodes?
Hi Robert,
After reading your email I have seen that in the configuration there are
two options about instance types, NODE_INSTANCE_TYPE
and MASTER_INSTANCE_TYPE
So the solution to achieve my desired setup seems to configure the master
to not being an exec node and select different type of instance for node
and master.
Thanks for your help and sorry for the beginner question...just doing my
first steps with starcluster
Pablo.
2014-10-24 13:27 GMT+02:00 Petit III, Robert A. <robert.petit_at_emory.edu>:
> Hi Pablo,
>
> If the master is set to not be an exec node, the worker nodes can be a
> different type. The situation you describe, (small master instance, large
> compute instances) is my current set up.
>
> I believe things are different when the master is set as an exec host.
>
> Cheers,
> Robert
>
> ------------------------------
> *From:* starcluster-bounces_at_mit.edu [starcluster-bounces_at_mit.edu] on
> behalf of Pablo Escobar [pescobar001_at_gmail.com]
> *Sent:* Friday, October 24, 2014 5:48 AM
> *To:* starcluster_at_mit.edu
> *Subject:* [StarCluster] is mandatory that master instance is the same
> kind of instance than compute nodes?
>
> Hi,
>
> I have been doing some testing with starcluster and I see that by
> default every machine is the same type of instance and that the sge_master
> is also an sge_exec node.
>
> I have read in the documentation that the sge plugin allows to configure
> the master node to not being an exec node.
>
> The ideal setup for me would be to have the master node being a small
> instance just running the sge_master and not running jobs and the compute
> nodes being bigger instances in terms of hardware resources.
>
> is this setup currently possible in starcluster? or is mandatory that
> every machine is the same kind of instance?
>
> thanks for your help.
>
> Pablo.
>
> ------------------------------
>
> This e-mail message (including any attachments) is for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this message (including any attachments) is strictly
> prohibited.
>
> If you have received this message in error, please contact
> the sender by reply e-mail message and destroy all copies of the
> original message (including attachments).
>
Received on Fri Oct 24 2014 - 07:33:33 EDT
This archive was generated by
hypermail 2.3.0.