Go to file
nicky f1592c42d9 Add a new configuration parameter rpc_response_max_timeout
A new parameter rpc_response_max_timeout is added and registered into
neutron.conf.

The rpc_response_max_timeout plays a role of the ceiling of timeout
seconds when waiting for the response of a remote rpc server.

During an RPC call, the waiting time starts from the existing parameter
rpc_response_timeout(default 60s) and doubled each time until it reaches
the ceiling which is currently set as 10 times rpc_response_timeout.
It seems to be less flexible since user cannot directly change the
ceiling value unless he/she changes the rpc_response_timeout.
By adding rpc_response_max_timeout, user can now modify it without
changing any other parameters.

Co-Authored-By: Allain Legacy<Allain.legacy@windriver.com>

Change-Id: I170113c2946cc95308edcb1a703a99c71e50b6f9
Related-Bug: #1805769
Story: 2004456
Task: 28171
2019-01-18 09:55:31 +00:00
2016-06-28 22:46:19 +02:00
2019-01-07 12:45:15 -05:00
2016-10-17 17:06:19 +05:30
2018-12-20 14:19:40 +09:00
2014-05-16 13:40:04 -04:00
2018-10-03 08:41:56 +00:00
2019-01-14 09:53:39 +00:00
2017-06-13 19:26:49 +00:00
2017-08-31 16:44:51 +02:00
2018-12-13 10:00:17 +00:00
2017-03-04 11:19:58 +00:00

Team and repository tags

image

Welcome!

To learn more about neutron:

Get in touch via email. Use [Neutron] in your subject.

To learn how to contribute:

CONTRIBUTING.rst

Description
OpenStack Networking (Neutron)
Readme 1 GiB
Languages
Python 99.7%
Shell 0.3%