You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* refactorize skylet
* implement autostop event without cluster stopping
* wip
* Remove autostop from yaml file
* fix naming
* fix config
* fix skylet
* add autostop to status
* fix state and name match
* Replace min_workers/max_workers for gcp
* using ray up / ray down process
* fix stopping
* set autostop in globle user state
* update sky status
* format
* Add refresh to sky status
* address comments
* comment
* address comments
* Fix logging
* update help
* remove ssh config and bring cursor back
* Fix exec on stopped instance
* address comment
* format
* fix
* Add test for autostop
* Fix cancel
* address comment
* address comment
* Fix sky launch will change autostop to -1
* format
* Add docs
* update
Sky's **auto-stopping** can automatically stop a cluster after a few minutes of idleness.
6
+
7
+
To setup auto-stopping for a cluster, :code:`sky autostop` can be used.
8
+
9
+
.. code-block:: bash
10
+
11
+
# Launch a cluster with logging detached
12
+
sky launch -c mycluster -d cluster.yaml
13
+
14
+
# Set auto-stopping for the cluster, after cluster will be stopped 10 minutes of idleness
15
+
sky autostop mycluster -i 10
16
+
17
+
The :code:`-d / --detach` flag detaches logging from the terminal.
18
+
19
+
To cancel the auto-stop scheduled on the cluster:
20
+
21
+
.. code-block:: bash
22
+
23
+
# Cancel auto-stop for the cluster
24
+
sky autostop mycluster --cancel
25
+
26
+
To view the status of the cluster:
27
+
28
+
.. code-block:: bash
29
+
30
+
# Show a cluster's jobs (IDs, statuses).
31
+
sky status
32
+
NAME LAUNCHED RESOURCES STATUS AUTOSTOP COMMAND
33
+
mucluster 1 min ago 2x AWS(m4.2xlarge) UP 0 min sky launch -d -c ...
34
+
35
+
# Refresh the status for auto-stopping
36
+
sky status --refresh
37
+
NAME LAUNCHED RESOURCES STATUS AUTOSTOP COMMAND
38
+
mucluster 1 min ago 2x AWS(m4.2xlarge) STOPPED - sky launch -d -c ...
39
+
40
+
41
+
The cluster status in :code:`sky status` shows the cached status of the cluster, which can be out-dated for clusters with auto-stopping scheduled. To view a real status of the cluster with auto-stopping scheduled, use :code:`sky status --refresh`.
0 commit comments