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

[Enhancement] Optimize Timer Message Retry Mechanism #8979

Open
1 task done
chi3316 opened this issue Nov 25, 2024 · 0 comments · May be fixed by #8980
Open
1 task done

[Enhancement] Optimize Timer Message Retry Mechanism #8979

chi3316 opened this issue Nov 25, 2024 · 0 comments · May be fixed by #8980

Comments

@chi3316
Copy link
Contributor

chi3316 commented Nov 25, 2024

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Improve the retry mechanism in TimerMessageStore to handle message processing failures more efficiently by refining retry limits and adding better fallback handling.

Motivation

The current retry mechanism lacks flexibility, which may lead to unintentional message loss. Adding a configurable switch ensures users can choose to retain unprocessed messages after retries

Describe the Solution You'd Like

  • Refine Retry Limits: Introduce a configurable retry limit to prevent endless retry loops.
  • Detailed Error Handling: Categorize errors to determine retry eligibility.

Describe Alternatives You've Considered

Skipping retries entirely for certain error types but discarded due to potential message loss.

Additional Context

No response

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

Successfully merging a pull request may close this issue.

1 participant