fix(contrib/registry/eureka): improve server picking and retry logic #3781
+11
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

This PR fixes potential issues in the Eureka client's server picking and retry logic.
e.maxRetryis not necessarily equal tolen(e.urls),because users can customize
e.maxRetryusing theWithMaxRetryfunction.When users set e.maxRetry=0, the for-loop in the
Client.domethod will not execute.When
e.maxRetryis greater thanlen(e.urls), array index out of bounds may occur.For example, if a user sets e.maxRetry=10 and len(e.urls)=2,
when
pickServeris executed with currentTimes=2,currentTimes%e.maxRetry=2, resulting in an array index out of bounds.