[
https://issues.apache.org/jira/browse/KNOX-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557903#comment-17557903
]
ASF subversion and git services commented on KNOX-2742:
-------------------------------------------------------
Commit 3b63b9851937b484546d974612e6ddd3ceaabbc9 in knox's branch
refs/heads/dependabot/npm_and_yarn/knox-token-management-ui/minimist-1.2.6 from
Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=3b63b9851 ]
KNOX-2742 - Retrying CM service discovery in case of ConnectExceptions (#571)
> CM service discovery retry may be needed
> ----------------------------------------
>
> Key: KNOX-2742
> URL: https://issues.apache.org/jira/browse/KNOX-2742
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If there is a connection issue the first time Knox discovers a cluster in CM,
> the topology will remain empty (bc. it was empty anyway). Fixing KNOX-2690
> should help here a lot but maybe it's not enough. We may add some sort of
> retry logic if service discovery failed due to communication errors.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
