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

config: enable user configuration for retry strategy. #1055

Merged
merged 3 commits into from
Nov 14, 2023

Conversation

Smityz
Copy link
Contributor

@Smityz Smityz commented Nov 10, 2023

We have observed that in some cases, the configuration of backoff has a significant impact on the delay. Therefore, we would like to provide the option for manual adjustment of the retry strategy on the client-side.
This PR moved folder internal/retry to config/retry

Signed-off-by: Smityz <[email protected]>
@disksing
Copy link
Collaborator

Thanks @Smityz

@disksing disksing merged commit 6ba909c into tikv:master Nov 14, 2023
9 of 10 checks passed
@ekexium
Copy link
Contributor

ekexium commented Feb 18, 2024

After this PR, two duplicate files of backoff.go exist: config/retry/backoff.go and internal/client/retry/backoff.go. What is the purpose of maintaining two copies? Is it possible to eliminate one of them?

@Smityz
Copy link
Contributor Author

Smityz commented Feb 29, 2024

After this PR, two duplicate files of backoff.go exist: config/retry/backoff.go and internal/client/retry/backoff.go. What is the purpose of maintaining two copies? Is it possible to eliminate one of them?

I'm sorry, I don't understand the difference between them. If a refactoring is needed, I am also willing to take this job

@ekexium
Copy link
Contributor

ekexium commented Feb 29, 2024

I'm just wondering why this PR both

  1. does a rename
image
  1. and creates new files
image

If this is by mistake, we can eliminate one of them

@Smityz
Copy link
Contributor Author

Smityz commented Feb 29, 2024

I'm just wondering why this PR both

  1. does a rename
image 2. and creates new files image If this is by mistake, we can eliminate one of them

Yes, it's a mistake. I will raise another PR to fix it. Thanks for your reminding

@Smityz Smityz mentioned this pull request Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants