Add driver ID to task spec and add driver ID to Python error handling. #225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This provides a small amount of isolation between different drivers using the same cluster (there is not much isolation at the moment, e.g., remote functions, environment variables, and such will conflict).
The following can be done to cause an error from one driver to be pushed to another driver.
From
ray/
start a local cluster withThen in two separate windows, attach drivers to the cluster by following the instructions printed out from the
start_ray.sh
command, e.g.,Then define a remote function on one of the drivers that throws an exception, and call it.
The error message should appear in both windows.