-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Remote call timeout required. #18916
Comments
Nice proposal.
|
What about child task and method calls? Do timeout / deadline propagate implicitly or explicitly? |
@mwtian , child tasks are automatically killed when the parent dies, so there's nothing that should need to happen for that to work. |
+1 on the proposal, but it should be |
@ericl Does the task canceling API apply to actor tasks? |
@iycheng is this part of Ray HA? |
this would be great feature to have. |
Any updates on this? |
Hi team, is there any progress on this? We would like to contribute if required. |
@MissiontoMars we'd like to work with you on this! Could you create a short REP (https://github.com/ray-project/enhancements) and we can go from there? |
Sounds good. Maybe I can submit a short REP in June. |
Search before asking
Description
Why the feature needed?
Feature required from our users. The current remote call design lacks a timeout mechanism,
actor.foo.remote()
will be executed in the end. The user may expect the remote call to be completed in a certain period of time, if not, then give up. If the producer actor send lots of calls in a short time, some calls which destined to be timeout will also be executed, that's unnecessary.API
Set
timeout_ms
option when do remote call. e.g.:When the caller actor send out the task, put the current timestamp in taskspec, and on the callee actor side, check the timestamp with current system time when prepare to execute the task, if timeout, give up.
Other considerations
Use case
No response
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: