Issue #915
closed
/status/ API does not report health of webservers
Description
When using the /status/ API to evaluate the health of a Pulp system, webserver availability and health information is not included. In a standalone installation this is not needed because the response code of 200 OK is intended to indicate the webserver is OK. In a clustered environment with multiple webservers, a /status/ request may be handled by a webserver who is online and functioning, while other webservers may be offline.
To workaround this limitation, it is recommended that all webservers in a cluster have the /status/ API call monitored directly (not through the load balancer). All webservers that are expected to be online should be checked that they return a '200 OK'.
This is likely not something Pulp can resolve currently because the load balancer is the component that knows which webservers to expect to be online or not. I propose this bug remain open to track this issue as a known limitation.
Added by bmbouter over 9 years ago
Added by bmbouter over 9 years ago
Revision e00e8d5a | View on GitHub
Adds three updates to the clustering documentation.
-
A section on clustered monitoring which identifies issues and workarounds for the /status/ API in clustered environments.
-
A section on pulp-admin configuration for clustered environments.
-
Generalizes the load balancer docs to include DNS based load balancing in addition to TCP based load balancing.
https://pulp.plan.io/issues/915 https://pulp.plan.io/issues/282
Updated by cduryee over 9 years ago
- Status changed from NEW to CLOSED - WONTFIX
- Triaged changed from No to Yes
marking issue as closed/wontfix. The workaround is documented in referenced commit.
.
Adds three updates to the clustering documentation.
A section on clustered monitoring which identifies issues and workarounds for the /status/ API in clustered environments.
A section on pulp-admin configuration for clustered environments.
Generalizes the load balancer docs to include DNS based load balancing in addition to TCP based load balancing.
re #915 re #282
https://pulp.plan.io/issues/915 https://pulp.plan.io/issues/282