Bug 1391375
Summary: | Please revisit the proxy timeout related settings | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> |
Component: | openstack-tripleo | Assignee: | Chris Jones <chjones> |
Status: | CLOSED DUPLICATE | QA Contact: | Arik Chernetsky <achernet> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 10.0 (Newton) | CC: | fdinitto, mburns, mcornea, michele, rhel-osp-director-maint, rohara, vcojot |
Target Milestone: | --- | Keywords: | InstallerIntegration |
Target Release: | 11.0 (Ocata) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-23 12:28:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Attila Fazekas
2016-11-03 08:13:24 UTC
Ryan, can you please check current OSP10 haproxy.conf and see what changes could/should be done? The timeout that is coming into play here is the 'timeout server 1m'. We've had other requests to increase this timeout in the past, but ultimately we choose not to because it never seems to be enough. If we increase the timeout to 2 minutes, next month somebody will want it to be 3 minutes, and next year 5 minutes. If glance and heat need longer timeouts, I suggest we set them in the proxy definition (listen or frontend block). This will override the timeout from defaults, but only for those proxies. Another 504 hit: https://bugzilla.redhat.com/show_bug.cgi?id=1394155 What would happen if you just delete that option ? Think in a different way for minute, what if I say proxy has to be at least as patient as the client ? (In reply to Attila Fazekas from comment #4) > Think in a different way for minute, what if I say proxy has to be at least > as patient as the client ? I don't understand this question. Patient in what way? Are you talking about the 'timeout client'? If the client itself is not giving up on waiting for the server, why the intermediate proxy would break the connection ? Why the proxy does not wait as long as the client is willing to wait ? Why the proxy thinks he can judge an openstack api service, and punishing it by breaking the client connection because of the server being slow ? <joking> If we would like to keep following the already implemented not patient pattern, I would recommend also automatically deleting the services when they are not responding in time, and I also recommend decreasing the time limit to 5 sec instead of 60sec. </joking> I read the haproxy doc, looks like the `doc` likes this limited timeout thing what we are doing now, but I have doubts about really it is the right way for any openstack service. *** This bug has been marked as a duplicate of bug 1289315 *** *** Bug 1593811 has been marked as a duplicate of this bug. *** |