
This change addresses a long-standing issue in rST documentation imported from XML. That import process added backslash escapes in front of various characters. The three most common being '(', ')', and '_'. These instances are removed. Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
54 lines
1.9 KiB
ReStructuredText
54 lines
1.9 KiB
ReStructuredText
|
||
.. gkr1591372948568
|
||
.. _adding-configuration-rpc-response-max-timeout-in-neutron-conf:
|
||
|
||
=============================================================
|
||
Add Configuration rpc_response_max_timeout in neutron.conf
|
||
=============================================================
|
||
|
||
You can add the rpc_response_max_timeout to neutron.conf using Helm
|
||
overrides.
|
||
|
||
.. rubric:: |context|
|
||
|
||
Maximum rpc timeout is now configurable by rpc_response_max_timeout from
|
||
Neutron config instead of being calculated as 10 \* rpc_response_timeout.
|
||
|
||
This configuration can be used to change the maximum rpc timeout. If maximum
|
||
rpc timeout is too big, some requests which should fail will be held for a long
|
||
time before the server returns failure. If this value is too small and the
|
||
server is very busy, the requests may need more time than maximum rpc timeout
|
||
and the requests will fail though they can succeed with a bigger maximum rpc
|
||
timeout.
|
||
|
||
.. rubric:: |proc|
|
||
|
||
#. create a yaml file to add configuration rpc_response_max_timeout in
|
||
neutron.conf.
|
||
|
||
.. code-block:: none
|
||
|
||
~(keystone_admin)]$ cat > neutron-overrides.yaml <<EOF
|
||
conf:
|
||
neutron:
|
||
DEFAULT:
|
||
rpc_response_max_timeout: 600
|
||
EOF
|
||
|
||
#. Update the neutron overrides and apply to |prefix|-openstack.
|
||
|
||
.. parsed-literal::
|
||
|
||
~(keystone_admin)]$ system helm-override-update |prefix|-openstack neutron openstack --values neutron-overrides.yaml
|
||
~(keystone_admin)]$ system application-apply |prefix|-openstack
|
||
|
||
#. Verify that configuration rpc_response_max_time has been added in
|
||
neutron.conf.
|
||
|
||
.. code-block:: none
|
||
|
||
$ kubectl get pod -n openstack | grep neutron
|
||
$ kubectl get pod -n openstack | grep neutron-server
|
||
$ kubectl exec <neutron-server-id> -n openstack – cat /etc/neutron/neutron.conf | grep rpc_response_max_timeout
|
||
rpc_response_max_timeout = 600
|
||
$ cat /etc/neutron/neutron.conf | grep rpc_response_max_timeout |