l3 agent can be marked dead while it reschedules a lot of resources
Bug #1440761 reported by
Ann Taraday
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Low
|
Unassigned |
Bug Description
If l3 agent get killed and there are a lot of resources assigned on it, the agent on which this resources are rescheduling can be marked as dead for neutron-server because state reports are not received in agent_down_time*2.
This was tested with agent_down_time=15 and 100 routers for rescheduling.
Changed in neutron: | |
assignee: | nobody → Ann Kamyshnikova (akamyshnikova) |
Changed in neutron: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
This is similar issue which was previously found for DHCP agent.
Since for L3 case it has less chances to appear (need many routers, low 'agent_down' parameters) setting the importance to 'Low'.
We need to give few additional seconds for L3 agent that has received a bunch of routers before considering it dead and moving routers from it.