wassname/ray
1
0
Fork 0
mirror of https://github.com/wassname/ray.git synced 2026-08-12 12:20:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

[autoscaling] increase connect timeout, boto retries, and check subnet conf (#1422)

Browse Source 
* some autoscaling config tweaks

* Sun Jan 14 13:56:55 PST 2018

* Mon Jan 15 14:21:09 PST 2018

* increase backoff

* Mon Jan 15 14:40:47 PST 2018

* check boto version
This commit is contained in:
Eric Liang
2018-01-16 16:11:09 -08:00
committed by GitHub
parent eac11c252c
commit b8811cbe34
5 changed files with 41 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/autoscaling.rst
+1 -1
View File
@@ -41,7 +41,7 @@ Autoscaling
Ray clusters come with a load-based auto-scaler. When cluster resource usage exceeds a configurable threshold (80% by default), new nodes will be launched up the specified ``max_workers`` limit. When nodes are idle for more than a timeout, they will be removed, down to the ``min_workers`` limit. The head node is never removed.
The default idle timeout is 5 minutes. This is because in AWS there is a minimum billing charge of 5 minutes per instance, after which usage is billed by the second.
The default idle timeout is 5 minutes. This is to prevent excessive node churn which could impact performance and increase costs (in AWS there is a minimum billing charge of 1 minute per instance, after which usage is billed by the second).
Monitoring cluster status
-------------------------