- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 02:35 AM
I have a cluster pool with a max capacity limit, to make sure we're not burning too extra silicon. We use this for some of our less critical workflow/jobs. They still spend a lot of time idle, but sometimes hit this max capacity limit. Is there a way to get a job to wait for an available pool instance, rather than automatically failing with an
instance_pool_error_code:INSTANCE_POOL_MAX_CAPACITY_FAILURE
?
- Labels:
-
Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 10:33 AM
@andyh did you get a chance to check queue in jobs, that may help, will update if we have any other options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 12:18 PM
Try increasing your max capacity limit and might want to bring down the min number of nodes the job uses.
At the job level try configuring retry and time interval between retries.
