Safe to use pool autoscaling with Batch Shipyard?
See original GitHub issueI’ve been setting pool autoscaling on pools created using Batch Shipyard pool add
, and I’ve been testing it out for a while now with no issues. I just wanted to confirm that Batch Shipyard is safe to use with autoscaling, and whether there are any considerations I should keep in mind? I’m not running multi-instance jobs.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Batch Shipyard and Pool Autoscaling - GitHub
Scenario-based autoscaling allows you to pick from a set of common autoscale scenarios and then Batch Shipyard automatically applies the appropriate ...
Read more >Data Movement - Batch Shipyard - Read the Docs
The focus of this article is to explain how to move data between on-premises, Azure storage and Batch compute nodes in the context...
Read more >Pool - Enable Auto Scale - REST API (Azure Batch Service)
Enables automatic scaling for a Pool. You cannot enable automatic scaling on a Pool if a resize operation is in progress on the...
Read more >Batch Shipyard | Simplify HPC and Batch workloads on Azure
Batch Shipyard supports both Docker and Singularity containers. No experience with the Azure Batch SDK is needed; run your containers with easy-to-understand ...
Read more >How to distribute large workloads using Azure Batch - YouTube
In this episode Marco Mansi introduces Azure Batch, one of the "OG" services that has been around for a while on Microsoft Azure....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for confirming. I will roll this into 2.6.2.
Awesome. We just tested out the
cli-develop
image, and it looks like it’s finding and pulling the missing Docker images from our Azure registry properly. Thanks for the quick fix!