Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add closer server to the NSMgr chain #1032

Closed
Bolodya1997 opened this issue Jul 20, 2021 · 2 comments
Closed

Add closer server to the NSMgr chain #1032

Bolodya1997 opened this issue Jul 20, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@Bolodya1997
Copy link

Issue

Client performs Close with some context timeout. It can be enough to reach NSMgr but in some cases (e.g. on high load) it can be not enough to pass the whole networkservice chain across all hops, so this Close would fail even it has reach the NSMgr.

Solution

Add closer server in the beginning of the NSMgr networkservice chain, so it would restart Close event on NSMgr application context with the bigger timeout.

References

#1031

@Bolodya1997 Bolodya1997 added the enhancement New feature or request label Jul 20, 2021
@edwarnicke
Copy link
Member

@Bolodya1997 Isn't this already taken care of by the Refresh timer?

@Bolodya1997
Copy link
Author

I guess this should be resolved by networkservicemesh/deployments-k8s#906, so we can close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants