-
Notifications
You must be signed in to change notification settings - Fork 10
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
Decommissioning a backend/disk causes connections leaks #618
Comments
@JeffreyDevloo , @pploegaert Do we have a test that deletes backends so we can reproduce this? |
Not to this extend. We currently just setup and alba backend, add a preset and then remove it. Also this ticket is rather vague. What happened here for instance? "After the proxy removed the backend from list-osds" would imply a global backend having other backends as osds where one of the backends would be removed from it while the global backend is being used on a vpool (hence the proxy reference)
|
@JeffreyDevloo please reproduce the scenario first so we know exactly how we got into it. |
We (pluralis majestatis) already know exactly how we got into it |
@domsj please explain. Is this still an issue? |
On a certain environment I've decommissioning a backend that is still running but policy wise broken.
After the proxy removed the backend from
list-osds
we would expect all connections died with it.But as seen here it isn't. (These results are for 12 ASDS)
The text was updated successfully, but these errors were encountered: