** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1817022
Title:
[RFE] set inactivity_probe and max_backoff for OVS bridge controller
Status in neutron:
Fix Released
Bug description:
It would be useful to have the option to specify inactivity_probe and
max_backoff for OVS bridge controllers in neutron config.
OVS documentation says
(https://github.com/openvswitch/ovs/blob/master/ovn/TODO.rst):
The default 5 seconds inactivity_probe value is not sufficient and
ovsdb-server drops the client IDL connections for openstack deployments when
the neutron server is heavily loaded.
This indeed can happen under the heavy load in neutron-ovs-agent. This
was discussed in http://eavesdrop.openstack.org/irclogs/%23openstack-
neutron/%23openstack-neutron.2017-01-27.log.html#t2017-01-27T02:46:22
, and the solution was to increase inactivity_probe.
Alternative is to set this settings manually after each neutron-ovs-agent
restart:
ovs-vsctl set Controller br-tun inactivity_probe=30000
ovs-vsctl set Controller br-int inactivity_probe=30000
ovs-vsctl set Controller br-ex inactivity_probe=30000
ovs-vsctl set Controller br-tun max_backoff=5000
ovs-vsctl set Controller br-int max_backoff=5000
ovs-vsctl set Controller br-ex max_backoff=5000
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1817022/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
