Review controller-max-backoff and controller-inactivity-probe values
Description
relates to
Activity
Sam Hague September 17, 2018 at 6:58 PM
https://git.opendaylight.org/gerrit/#/c/51763/
controller-inactivity-probe was bumped to 30s
Done
Details
Details
Assignee
Unassigned
UnassignedReporter
Sam HagueLabels
Components
Priority
Medium
Created November 28, 2017 at 3:09 PM
Updated September 17, 2018 at 6:59 PM
Resolved September 17, 2018 at 6:59 PM
Should the the two values are used to configure how the ovs nodes connect to ODL be changed from the defaults?
controller-max-backoff: max time between connection attempts from the nodes to ODL
controller-inactivity-probe: time between sending inactivity probes on connections
The defaults are 8s and 5s. If the inactivity-probe hits, then the switches disconnect from ODL. That cleans up the openflowplugin operational data for the node. That is then relayed to networking-odl that the node is down and networking-odl marks the node as inactive. When a node is down, networking-odl driver would mark port-binding as failed, so VM would enter ERROR state