mirror of
https://github.com/vale981/ray
synced 2025-03-10 13:26:39 -04:00
c8f207f746
This PR makes a number of major overhauls to the Ray core docs:
Add a key-concepts section for {Tasks, Actors, Objects, Placement Groups, Env Deps}.
Re-org the user guide to align with key concepts.
Rewrite the walkthrough to link to mini-walkthroughs in the key concept sections.
Minor tweaks and additional transition material.
13 lines
977 B
ReStructuredText
13 lines
977 B
ReStructuredText
Fault Tolerance
|
|
===============
|
|
|
|
Typical use of objects is covered by :ref:`task <task-fault-tolerance>` and :ref:`actor <actor-fault-tolerance>` fault tolerance. This section covers more advanced fault tolerance situations that may occur if passing objects by reference around in a Ray application.
|
|
|
|
Object Ownership and Fault Tolerance
|
|
------------------------------------
|
|
|
|
Ray delegates the metadata tracking of an object to its *owner process*. Typically, the owner of an object is the worker that created it via ``ray.put()``, or the worker that submitted the task generating an object. For example, the owner of an object could be an actor or the driver process.
|
|
|
|
The owner of the object tracks the location and reference count for an object. If the owner process is unexpectedly killed, then the object cannot be recovered, even via lineage reconstruction.
|
|
|
|
For more information about how object ownership works, see the :ref:`Ray Architecture Whitepaper <whitepaper>`.
|