Skip to content

KNOX-2742 - Retrying CM service discovery in case of ConnectExceptions#571

Merged
smolnar82 merged 1 commit intoapache:masterfrom
smolnar82:KNOX-2742
May 11, 2022
Merged

KNOX-2742 - Retrying CM service discovery in case of ConnectExceptions#571
smolnar82 merged 1 commit intoapache:masterfrom
smolnar82:KNOX-2742

Conversation

@smolnar82
Copy link
Copy Markdown
Contributor

@smolnar82 smolnar82 commented May 9, 2022

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:

  • configured gateway.cloudera.manager.service.discovery.maximum.retry.attemps to 20 in gateway-site.xml
  • declared a descriptor with valid CM service discovery params
  • started Knox in a way such as it started 20-30 seconds earlier than the configured Cloudera Manager server. In the logs I saw the retry attempt, and, finally, the successful service discovery.

@smolnar82 smolnar82 self-assigned this May 10, 2022
@smolnar82 smolnar82 merged commit 3b63b98 into apache:master May 11, 2022
@smolnar82 smolnar82 deleted the KNOX-2742 branch May 11, 2022 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant