KNOX-2742 - Retrying CM service discovery in case of ConnectExceptions#571
Merged
smolnar82 merged 1 commit intoapache:masterfrom May 11, 2022
Merged
KNOX-2742 - Retrying CM service discovery in case of ConnectExceptions#571smolnar82 merged 1 commit intoapache:masterfrom
smolnar82 merged 1 commit intoapache:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
In case of
ConnectExceptions coming from Cloudera Manager during service discovery, Knox may re-try connecting to CM every 3 seconds for the configured number of times in order to successfully discover the configured cluster for the configured descriptor.How was this patch tested?
In addition to adding new unit tests, I manually tested the solution:
gateway.cloudera.manager.service.discovery.maximum.retry.attempsto 20 ingateway-site.xml