Closed rvencu closed 2 years ago
Absolutely, make sense. The reason why I used this instance is because it is within the free tier but feel free to set a bigger one here: https://github.com/aws-samples/1click-hpc/blob/main/Templates/AWS-HPC-Cluster.yaml#L84
Yes, what I am saying, setting it differently still result in getting db.t4g.micro
No idea why it happens
so, what you are saying is that you have a different instance type in your custom CF template set accordingly to the region where you plan to deploy the new cluster, then you built a new cluster using your template and you are still getting the t4g ? (please note I fear stack updates are not supported)
Yes. It seems weird but this is what happens. For good measure I put all regions with same other instance type and still getting the t4g one
With a clean, new install
Obțineți Outlook pentru iOShttps://aka.ms/o0ukef
De la: Nicola Venuti @.> Trimis: Tuesday, July 12, 2022 12:56:34 PM Către: aws-samples/1click-hpc @.> Cc: Richard Vencu @.>; Author @.> Subiect: Re: [aws-samples/1click-hpc] Slurm DB always get set as db.t4g.micro no matter what option is used (Issue #30)
so, what you are saying is that you have a different instance type in your custom CF template set accordingly to the region where you plan to deploy the new cluster, then you built a new cluster using your template and you are still getting the t4g ? (please note I fear stack updates are not supported)
— Reply to this email directly, view it on GitHubhttps://github.com/aws-samples/1click-hpc/issues/30#issuecomment-1181615783, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AACGFMZWDEKXIA2L3FBFVHLVTVFOFANCNFSM53KP527Q. You are receiving this because you authored the thread.Message ID: @.***>
there must be something wrong, can you please hardcode the instance type, like:
DBInstanceClass: 'db.m6gd.16xlarge'
and try again
Thanks
tested with DBInstanceClass: 'db.m6g.8xlarge'
and I still get the t4g
need bigger instances cause for large fleets this small instance db.t4g.micro is unable to respond in time when large jobs are launched