You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
denis-tingaikin
changed the title
Rework discovery+roundrobin
roundrobin should work correctly in case if selected endpoint is busy
Nov 20, 2020
denis-tingaikin
changed the title
roundrobin should work correctly in case if selected endpoint is busy
roundrobin should work correctly in case if selected endpoint returns error
Nov 20, 2020
denis-tingaikin
changed the title
roundrobin should work correctly in case if selected endpoint returns error
roundrobin should handle a case if selected endpoint returns error
Nov 20, 2020
Actual behavior
Currently,
roundrobin
fails if the selected endpoint is busy or returns an error https://github.com/networkservicemesh/sdk/blob/master/pkg/networkservice/common/roundrobin/server.go#L63OR The same problem with other scerio:
Actual: NSC fails due to roundrobin selects bad NSE and not tries to select working NSE.
Expected behaviour
roundrobin
should try to select next endpoint if the previous one fails.Potential solution
rounrobin
should iterate over all Candidates in round-robin sequence.discovery
should try to call next with new candidates if they've registered during request AND previous candidates fail AND ctx is not done.The text was updated successfully, but these errors were encountered: