Decrease rpc timeout after agent receives SIGTERM
Added a note on configuring rpc timeout when the OVS agent receives SIGTERM. Change-Id: I26797935f42ad9ac26472cd783befc54efa3607b Closes-Bug: #1420773
This commit is contained in:
parent
e790ee9038
commit
59f02ddec0
@ -97,6 +97,14 @@ tenant_network_type=gre
|
||||
tunnel_id_ranges=1:1000
|
||||
# only required for nodes running agents
|
||||
local_ip=<replaceable>DATA_NET_IP_NODE_ADDRESS</replaceable></programlisting>
|
||||
<note>
|
||||
<para>Since the Kilo release you can set the
|
||||
<option>quitting_rpc_timeout</option> option
|
||||
with a timeout value for RPC API objects. This prevents
|
||||
a long waiting for RPC calls after <literal>SIGTERM</literal> is
|
||||
received which results in decreasing the amount of time needed to
|
||||
successfully stop the OVS agent.</para>
|
||||
</note>
|
||||
<para>For database configuration, see <link
|
||||
xlink:href="http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-controller-node.html"
|
||||
>Install Networking Services</link> in the <citetitle>Installation
|
||||
|
Loading…
Reference in New Issue
Block a user