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

Small improvements to using ray on large cluster documentation. (#573)

Browse Source
This commit is contained in:
Robert Nishihara
2017-05-19 16:13:50 -07:00
committed by Philipp Moritz
parent b62693ca67
commit 3d2f1b1941
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/using-ray-on-a-large-cluster.rst
+4 -2
View File
@@ -36,7 +36,7 @@ Additional assumptions:
* The head node will run Redis and the global scheduler.
* The head node has ssh access to all other nodes.
* All nodes are accessible via ssh keys
* Ray is checked out on each node at the location `$HOME/ray`.
* Ray is checked out on each node at the location ``$HOME/ray``.
**Note:** The commands below will probably need to be customized for your
specific setup.
@@ -248,7 +248,9 @@ Next run the upgrade script on the worker nodes.
parallel-ssh -h workers.txt -P -t 0 -I < upgrade.sh
Note here that we use the ``-t 0`` option to set the timeout to infinite.
Note here that we use the ``-t 0`` option to set the timeout to infinite. You
may also want to use the ``-p`` flag, which controls the degree of parallelism
used by parallel ssh.
It is probably a good idea to ssh to one of the other nodes and verify that the
upgrade script ran as expected.