diff options
| author |   Emilien Macchi <emilien@redhat.com> | 2017-04-17 11:30:23 -0400 |
|---|---|---|
| committer | Emilien Macchi <emilien@redhat.com> | 2017-04-17 21:07:36 +0000 |
| commit | 6cb95e6a69677755a070cc73062b70c84452824e (patch) | |
| tree | 081c7fd14b2a3411466cce43b885ce0db38d4a4b /releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml | |
| parent | 7b08425741e4e49c8ea1c3ca34e5797fd24cce05 (diff) | |
HAproxy/heat_api: increase timeout to 10m
Default timeout is 2min but it doesn't reflect the rpc_response_timeout
value that we set in THT and instack-undercloud, which is 600 (10 min).
In some cases (in low-memory environments), Heat needs more than 2
minutes to reply to the client, when deploying the overcloud.
It makes sense to increase the timeout to the value of rpc_timeout to
give a chance to Heat to reply to the client, otherwise HAproxy will
kill the connection and send 504 to the client.
Depends-On: I9669d40d86d762101734704fcef153e360767690
Change-Id: I32c71fe7930c8798d306046d6933e4b20c22740c
Related-Bug: 1666072
Diffstat (limited to 'releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml')
| -rw-r--r-- | releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml b/releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml new file mode 100644 index 0000000..a3b7d91 --- /dev/null +++ b/releasenotes/notes/heat_api_timeout-cbb01242534cec79.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - For Heat API, increase the HAproxy timeout from 2 minutes to 10 minutes so + we give a chance to Heat to use the rpc_response_timeout value which is set + to 600 by default in TripleO. |