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

[Feature][SDK] InlongSDK support retry sending when failed #10464

Closed
1 of 2 tasks
Tracked by #10497
vernedeng opened this issue Jun 19, 2024 · 2 comments · Fixed by #11144
Closed
1 of 2 tasks
Tracked by #10497

[Feature][SDK] InlongSDK support retry sending when failed #10464

vernedeng opened this issue Jun 19, 2024 · 2 comments · Fixed by #11144

Comments

@vernedeng
Copy link
Contributor

vernedeng commented Jun 19, 2024

Description

When InlongSDK fails to send data to DataProxy, it returns the failure to the user directly. Add the capability to retry sending.

image

Location:
inlong-sdk/dataproxy-sdk/

Requirements:

  1. Choose another dataproxy node to resend data when the send fails.
  2. Able to configure max retry times.
  3. Check failures and only retry those retriable, discard those not.

This issue is a dedicated issue for the 2024 Tencent Rhino-bird Open Source Talent Training event and is only available for college students to claim
【Claim the issue】Sign up for the corresponding issue in columns M~R of the Research and Study Base "issue Camp" to be considered as successfully claimed.
【Complete the issue】For students who have claimed the issue, please also reply "Successfully claimed this issue" in the comment section of this issue; if there is no progress submitted within 7 days, including but not limited to comments, commits, or Pull Requests, it will be considered as voluntarily giving up the issue and the committee will release the issue to the next person in line.

Use case

No response

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@vernedeng vernedeng added this to the 1.13.0 milestone Jun 19, 2024
@vernedeng vernedeng self-assigned this Jun 19, 2024
@vernedeng vernedeng removed this from the 1.13.0 milestone Jun 25, 2024
@vernedeng vernedeng removed their assignment Jun 25, 2024
@Hackerismydream
Copy link

Successfully claimed this issue

Copy link

This issue is stale because it has been open for 60 days with no activity.

@github-actions github-actions bot added the stage/stale Issues or PRs that had no activity for a long time label Aug 28, 2024
@dockerzhang dockerzhang added this to the 1.14.0 milestone Sep 19, 2024
@github-actions github-actions bot removed the stage/stale Issues or PRs that had no activity for a long time label Sep 20, 2024
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.

3 participants