Thanks for the reply. I just realized submitting a job with 1 node with slurm, launches compute001 although I did not specify the node. Seems like elasticluster does not intend to use frontend for computations. I don't know if should I ask this question in separate post but is it possible to launch the high-memory requiring job on frontend instead of compute node? If this is not possible, then how can I make two sections for compute nodes instead of sectioning compute and frontend?
On Tue, Dec 18, 2018 at 1:13 PM Manuele Simi <[email protected]> wrote: > Yes, it is possible. > > You need to define a cluster/<name>/<group> sections that override the > cluster/<name> section. > > In the following example I create specific configurations (with their own > flavor) for the nodes in the compute and frontend groups of a cluster named > "gridengine". > > # Cluster Section > *[cluster/gridengine]* > ... > *frontend_nodes=1* > *compute_nodes=3* > > # Compute node section > *[cluster/gridengine/compute]* > *flavor=n1-highcpu-2* > ... > > # Frontend node section > *[cluster/gridengine/frontend]* > *flavor=n1-standard-64* > ... > > On Tue, Dec 18, 2018 at 8:46 AM Orxan Shibliyev <[email protected]> > wrote: > >> Is it possible to take different flavors for frontend and compute nodes? >> I want high memory machine for frontend and lower memory for computes. I >> use GCE machines. >> >> -- >> 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. >> > -- 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.
