Improve logic that determines liveliness of dhcp agent
Bug #1417708 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Eugene Nikanorov |
Bug Description
It has been revealed that under load (when a bunch of networks is processed) DHCP agent fails to send heartbeat updates and neutron-server starts to consider it dead.
In network failover feature this has been worked around by checking if DHCP agent has just started up and giving it amount of time proportional to number of networks scheduled to it.
However in scheduling logic there's no such additional liveliness conditions, so starting agent may be considered dead and network will be scheduled on additional agent beyond configured limit.
So in order to avoid such negative side effect, agent liveliness check logic needs to be unified.
Changed in neutron: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
what do u mean by 'network failover feature'? where is the feature?