Possible scale issues with neutron-fwaas requesting all tenants with firewalls after RPC failures
Bug #1618244 reported by
Sridar Kandaswamy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Low
|
Bertrand Lallau |
Bug Description
Information zzelle in conversation with njohnston
An overload is caused first by some neutron-servers crashed, secondly by every l3-agent trying to perform a "full" process_
About 60 L3Agents, with one router per L3Agent.
Key question: typically i don't understand why in full sync a l3-agents request tenants with FWs intead of requesting its tenants with FW ?
tags: | added: fwaas |
Changed in neutron: | |
assignee: | nobody → Bertrand Lallau (bertrand-lallau) |
status: | New → Confirmed |
Changed in neutron: | |
assignee: | Bertrand Lallau (bertrand-lallau) → Reedip (reedip-banerjee) |
Changed in neutron: | |
assignee: | Reedip (reedip-banerjee) → Bertrand Lallau (bertrand-lallau) |
Changed in neutron: | |
importance: | Undecided → Low |
To post a comment you must log in.
zzelle, thanks for bringing this up. I think what u are raising is - perhaps a change along the lines to check which routers are part of the specific L3Agent and get the firewalls corresponding to just those tenants is what u are asking for should bring down the scale in comparison to get all the tenants with firewalls.
One thing i also wanted to understand is that in terms of the messaging right after a recovery from an RPC failure - each agent will still check to see if it has firewalls associated, so we will have all these agents trying to ask the plugin, so the messaging may not quite come down. Perhaps we can this conversation to triage this to see what is the best way to move fwd and we can address that.