ray/ci/long_running_tests
Eric Liang 904dcf081d
Switch cluster longevity tests to DLAMI, fix ray up verbosity (#5084)
* fix

* add branch commit

* comments

* Update ci/long_running_tests/.gitignore

Co-Authored-By: Robert Nishihara <robertnishihara@gmail.com>
2019-07-02 00:19:05 -07:00
..
workloads [tune] Directional metrics for components (#4120) (#4915) 2019-06-02 22:13:40 -07:00
.gitignore Switch cluster longevity tests to DLAMI, fix ray up verbosity (#5084) 2019-07-02 00:19:05 -07:00
check_workloads.sh [rllib] Add three new long-running stress tests {APEX, IMPALA, PBT} (#4215) 2019-03-04 14:05:42 -08:00
config.yaml Switch cluster longevity tests to DLAMI, fix ray up verbosity (#5084) 2019-07-02 00:19:05 -07:00
README.rst Make some fixes to long running stress tests. (#5056) 2019-06-28 15:42:54 -07:00
shut_down_workloads.sh [rllib] Add three new long-running stress tests {APEX, IMPALA, PBT} (#4215) 2019-03-04 14:05:42 -08:00
start_workloads.sh Switch cluster longevity tests to DLAMI, fix ray up verbosity (#5084) 2019-07-02 00:19:05 -07:00

Long Running Tests
==================

This directory contains scripts for starting long-running workloads which are
intended to run forever until they fail.

Running the Workloads
---------------------

To run the workloads, run

.. code-block:: bash

    ./start_workloads.sh <ray-branch> <ray-version> <ray-commit>

using the appropriate values of ``<ray-branch>``, ``<ray-version>``, and
``<ray-commit>``. This will start one EC2 instance per  workload and will start
the workloads running (one per instance). Running the ``./start_workloads.sh``
script again will clean up any state from the previous runs and will start the
workloads again.

Check Workload Statuses
-----------------------

To check up on the workloads, run either ``./check_workloads.sh --load``, which
will print the load on each machine, or ``./check_workloads.sh --logs``, which
will print the tail of the output for each workload.

To debug workloads that have failed, you may find it useful to ssh to the
relevant machine, attach to the tmux session (usually ``tmux a -t 0``), inspect
the logs under ``/tmp/ray/session*/logs/``, and also inspect
``/tmp/ray/session*/debug_state.txt``.

Shut Down the Workloads
-----------------------

The instances running the workloads can all be killed by running
``./shut_down_workloads.sh``.

Adding a Workload
-----------------

To create a new workload, simply add a new Python file under ``workloads/``.