mirror of
https://github.com/vale981/ray
synced 2025-03-08 19:41:38 -05:00
681e8cd3fd
## What do these changes do?
This option goes along with `min_workers`, and `max_workers`. When the
cluster is first brought up (or when it is refreshed with a subsequent
`ray up`) this number of nodes will be started.
It's a workaround for issues of scaling (see related issues) where it
can take a long time (or forever in the case where the head node has
`--num-cpus 0`) to scale up a cluster in response to increasing demand.
## Related issue number
Workaround for https://github.com/ray-project/ray/issues/3339 and https://github.com/ray-project/ray/issues/2106
|
||
|---|---|---|
| .. | ||
| jenkins_tests | ||
| stress_tests | ||
| travis-ci | ||
| actor_test.py | ||
| array_test.py | ||
| autoscaler_test.py | ||
| component_failures_test.py | ||
| credis_test.py | ||
| cython_test.py | ||
| failure_test.py | ||
| microbenchmarks.py | ||
| monitor_test.py | ||
| multi_node_test.py | ||
| multi_node_test_2.py | ||
| node_manager_test.py | ||
| object_manager_test.py | ||
| recursion_test.py | ||
| runtest.py | ||
| stress_tests.py | ||
| tempfile_test.py | ||
| tensorflow_test.py | ||
| xray_test.py | ||