healthchecks can fail due to mod_wsgi lazy loading
Bug #1846322 reported by
Oliver Walsh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
High
|
Unassigned |
Bug Description
(forked from https:/
From mod_wsgi FAQ https:/
Q: Why do requests against my application seem to take forever, but then after a bit they all run much quicker?
A: This is because mod_wsgi by default performs lazy loading of any application....
Where haproxy is not used this initial request is likely to be a healthcheck. The timeout on the healthcheck is 10s which *can* be exceeded.
Where haproxy is used the haproxy check requests appear to trigger lazy loading almost immediately after the container starts.
Changed in tripleo: | |
importance: | Undecided → High |
milestone: | none → train-rc1 |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | train-rc1 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
tags: | added: train-backport-potential |
tags: | added: queens-backport-potential |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.