-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
spring.cloud.config.retry.useRandomPolicy not being applied #2379
Comments
Yeah I think you are right. You are using bootstrap configuration then and not leveraging |
Yes, that's correct. |
ryanjbaxter
added a commit
to ryanjbaxter/spring-cloud-config
that referenced
this issue
Feb 1, 2024
ryanjbaxter
added a commit
that referenced
this issue
Feb 1, 2024
Fixes #2379 Co-authored-by: Ryan Baxter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see in #2353, that support was added for the
spring.cloud.config.retry.useRandomPolicy
property. However, it's not actually being applied when I run one of our ConfigServer clients. (I observed this by adding a break point inRetryProperties,isUseRandomPolicy()
. It's never being called. Note that we havespring.config.use-legacy-processing=true
.Analysis: The retry appears to be configured in ConfigServiceBootstrapConfiguration.configServerRetryInterceptor. In spring-cloud-config-client-4.0.5.jar, I see that the RetryInterceptorBuilder is not calling the retryPolicy builder method. Was that a miss in the above-mentioned PR?
The text was updated successfully, but these errors were encountered: