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

Check health of backends for which no proxies are deployed #309

Open
domsj opened this issue Mar 9, 2017 · 4 comments
Open

Check health of backends for which no proxies are deployed #309

domsj opened this issue Mar 9, 2017 · 4 comments

Comments

@domsj
Copy link

domsj commented Mar 9, 2017

The healthcheck does the following for all presets on all proxies: create-namespace, upload-object, delete-object, delete-namespace.

I think it would be a good idea to also do this for backends which have no proxies.
This can e.g. be the case for all flash backends which are only used for (fragment) caching.

@matthiasdeblock
Copy link
Contributor

Please be aware of the fact that you also need to check the puts to that backend to another node. In that case you also check if the disks on that other node is reachable over the network.

Had this issue today at GIG. The cache backend wasn't reachable from the controller/volumedrivernodes due to non reachable nodes over the storage IP.

@domsj
Copy link
Author

domsj commented Mar 10, 2017

Another point of view is: the proposed test could be done from any node (wherever is mot convenient to run it).
And another check is added to the healthcheck to verify network connectivity between all nodes.

@domsj
Copy link
Author

domsj commented Mar 11, 2017

Hmm, another way to look at it: the check should be done from each node where at least 1 proxy uses this backend as a fragment cache.

@wimpers wimpers added this to the Roadmap milestone Jun 13, 2017
@wimpers
Copy link

wimpers commented Jun 13, 2017

We need a way to test a fragment cache when there is no proxy deployed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants