Skip to content
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

Cancel/Kill and retry invocation from Admin API #895

Open
Tracked by #891 ...
slinkydeveloper opened this issue Nov 20, 2023 · 0 comments
Open
Tracked by #891 ...

Cancel/Kill and retry invocation from Admin API #895

slinkydeveloper opened this issue Nov 20, 2023 · 0 comments
Labels
admin good first issue Good for newcomers ops-ex Restate operational experience

Comments

@slinkydeveloper
Copy link
Contributor

slinkydeveloper commented Nov 20, 2023

Allow to issue a cancel/kill command and retry immediately after the kill/cancel happened. This can be useful in many situations, e.g.:

  • You want to retain invocation ordering on keyed services, but one invocation is stuck. You fix the service, deploy it, and then execute cancel/kill and retry (you might have to be able to delay the execute the old cancellations code).
  • You need to retry, but the invocation came from another service and you don't have the payload of the request at hand for retrying it manually
@slinkydeveloper slinkydeveloper added admin api-devex Restate user facing Development model labels Nov 20, 2023
@slinkydeveloper slinkydeveloper added the good first issue Good for newcomers label Jan 30, 2024
@slinkydeveloper slinkydeveloper added ops-ex Restate operational experience and removed api-devex Restate user facing Development model labels May 14, 2024
@slinkydeveloper slinkydeveloper changed the title Cancel/Kill and retry Cancel/Kill and retry invocation from Admin API Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin good first issue Good for newcomers ops-ex Restate operational experience
Projects
None yet
Development

No branches or pull requests

1 participant