Comment 2 for bug 1497219

Revision history for this message
Oleg Bondarev (obondarev) wrote :

Most probably the issue happens when one (or all) of l3 agents from controllers starts to resync. That may happen due to agent restart or some exception (like messaging exception). On resync agent requests full info for all routers scheduled to this agent - and this might be a really big amount of data if there are a lot of routers (like in create_and_list_routers rally scenario). This leads to 'Serious memory consumption by neutron-server'.

The idea of the fix is to request routers info by chunks (for example not more than 200 routers at a time).