[
https://issues.apache.org/jira/browse/KNOX-2742?focusedWorklogId=768171&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768171
]
ASF GitHub Bot logged work on KNOX-2742:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/May/22 20:24
Start Date: 09/May/22 20:24
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #571:
URL: https://github.com/apache/knox/pull/571
## What changes were proposed in this pull request?
TODO
## How was this patch tested?
TODO
Issue Time Tracking
-------------------
Worklog Id: (was: 768171)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
