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

Message failed state #671

Closed
Tracked by #549
nplasterer opened this issue Apr 18, 2024 · 0 comments · Fixed by #902
Closed
Tracked by #549

Message failed state #671

nplasterer opened this issue Apr 18, 2024 · 0 comments · Fixed by #902
Assignees

Comments

@nplasterer
Copy link
Contributor

          In the follow up PR we should do the following
  1. Mark the optimistic message as FAILED whenever its intent is marked as failed (set_group_intent_error)
  2. Make sure that every possible error case in this method results in the corresponding intent either being marked as TO_PUBLISH or FAILED
  3. At some point in the future revisit whether there is a possibility of an infinite loop of intent retries. Maybe we should call increment_intent_publish_attempt_count() wherever we reset an intent to TO_PUBLISH, and just set a really high retry limit, like 10?

For (2), maybe the most fool-proof way is to mark all MessageProcessingErrors as either retryable or non-retryable, and have the caller of the method catch all errors and mark the intent as TO_PUBLISH for retryable errors and FAILED for non-retryable errors

Originally posted by @nplasterer in #669 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants