-
Notifications
You must be signed in to change notification settings - Fork 49
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
Introduce retry-policy to shuffle #2148
Comments
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 7, 2024
Merged
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 7, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 7, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 7, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 8, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 29, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 29, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 29, 2024
Propagate shuffler error to PP instead of crashing the entire node Fixes restatedev#2148
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Dec 3, 2024
Propagate shuffler error to PP instead of crashing the entire node Fixes restatedev#2148
muhamadazmy
added a commit
that referenced
this issue
Dec 3, 2024
Propagate shuffler error to PP instead of crashing the entire node Fixes #2148
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the shuffle retries appending messages to bifrost indefinitely with a fixed delay. Changing this to a retry policy will allow to configure different strategies and also opens up the option for a finite policy.
The text was updated successfully, but these errors were encountered: