Cluster update times out while fetching compute node LaunchTemplates for queues #7519

Activity

1. hgreebe commented on Aug 5, 2026

   

   hgreebe

   on Aug 5, 2026

   Contributor

   More actions

   Hello,
   Could you provide a cluster configuration and what update you are making?
   How many queues are in your cluster?
2. inoue-hideki-a-opc commented on Aug 19, 2026

   

   inoue-hideki-a-opc

   on Aug 19, 2026

   Author

   More actions

   @hgreebe Thank you for your reply. Our configuration is as follows. Although there are 23 queues, since we have an internal proxy set up, it’s possible that communication with the AWS API from the Head Node is taking some time. I’m not entirely sure about the specific changes made to the cluster, but I believe we added about one or two queues.

   Region: us-east-1
   
   Image:
     Os: ubuntu2404
   
   SharedStorage:
     - Name: apps
       StorageType: Ebs
       MountDir: /shared
       EbsSettings:
         VolumeType: gp2
         Size: 200
   
   HeadNode:
     InstanceType: t3a.large
     Networking:
       SubnetId: subnet-00000000000000000
       ElasticIp: false
       Proxy:
         HttpProxyAddress: http://proxy.example.com:8080
     Ssh:
       KeyName: example-pcluster-key
       AllowedIps: 172.16.0.0/12
     LocalStorage:
       RootVolume:
         Size: 100
     Dcv:
       Enabled: false
   
   Monitoring:
     Logs:
       CloudWatch:
         Enabled: true
         RetentionInDays: 180
   
   Scheduling:
     Scheduler: slurm
     ScalingStrategy: all-or-nothing
     SlurmSettings:
       ScaledownIdletime: 10
       QueueUpdateStrategy: DRAIN
       Database:
         Uri: example-slurmdb-instance.abcdefghijkl.us-east-1.rds.amazonaws.com
         UserName: admin
         PasswordSecretArn: arn:aws:secretsmanager:us-east-1:000000000000:secret:/example-pcluster/slurmdbdPassword-xxxxxx
     SlurmQueues:
       - Name: q-example-gpu-single
         CapacityType: ONDEMAND
         ComputeResources:
           - Name: g4dnxlarge
             Instances:
               - InstanceType: g4dn.xlarge
             MinCount: 0
             MaxCount: 50
         Networking:
           SubnetIds:
             - subnet-00000000000000000
             - subnet-00000000000000001
           Proxy:
             HttpProxyAddress: http://proxy.example.internal:8080
     [... and 22 queues]
   
3. gmarciani

   added

   Backlog

   on Sep 8, 2026