Jobs Stuck in Runnable State
When submitting a rendering job, it may get stuck in the "Runnable/Pending" state due to various reasons.
Table of contents
Lack of Instances (Spot/On-Demand)
This can occur if there are no instances available at that time, especially if spot instances are being used. It is recommended to:
- Wait a few minutes and try again.
- Create stacks in other regions to check for resource availability.
Insufficient Quota
On GPU-based EC2 servers, it's common to face limitations on default quotas. It is suggested to:
- Request an increase in spot and on-demand instance quotas through the Brender Studio.
- Review and adjust quotas by region, as they are associated with specific regions and must be requested separately.
- Contact AWS Support if assistance is needed with the quota increase process.
Invalid Compute Environment
Check the status of compute environments and ensure they are all valid. In case of an invalid compute environment:
- Delete and recreate the corresponding farm stack.
- Ensure farm stacks are up to date and have the latest configuration.