Comment 4 for bug 1440761

I don't want to dismiss @Assaf's question so quickly. I'm not sure that I'm quite satisfied that is has been resolved.

The number of worker threads should be very limited in the L3 agent. The _process_routers_loop method limits the pool to a size of 8 threads. Also, there is a lot of IO going on in each of these threads. My experience is that each thread yields regularly. How is the state reporting getting starved? I restart production L3 agents routinely and we don't see this issue of the agent being reported as dead by the neutron server. We have in the 100s of routers per agent.