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

Support custom exception retry #1362

Open
EvenLjj opened this issue Sep 10, 2023 · 1 comment
Open

Support custom exception retry #1362

EvenLjj opened this issue Sep 10, 2023 · 1 comment
Labels
good first issue Good for newcomers later This will be worked on in later version

Comments

@EvenLjj
Copy link
Collaborator

EvenLjj commented Sep 10, 2023

Background

Due to the issue of idempotence, the SOFARPC retry framework cannot support retries for all exceptions. The current retry framework of SOFARPC only supports client timeout and server busy abnormal retries. It does not meet the requirements for business parties to flexibly use the RPC framework for retry.

What we hope to achieve

We can support the retry of custom exceptions, allowing users to confirm whether the exception can be retried.

@EvenLjj EvenLjj added the good first issue Good for newcomers label Sep 10, 2023
Copy link

stale bot commented Nov 10, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 10, 2023
@stale stale bot closed this as completed Nov 18, 2023
@OrezzerO OrezzerO reopened this Nov 30, 2023
@stale stale bot removed the wontfix This will not be worked on label Nov 30, 2023
@EvenLjj EvenLjj added the later This will be worked on in later version label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers later This will be worked on in later version
Projects
None yet
Development

No branches or pull requests

2 participants