Yeah, I was making a bad assumption for the l2 and l3. Sorry about that. It sounds like we don't have any protection against servers failing to send notifications. On Mar 12, 2015 7:41 PM, "Assaf Muller" <amuller at redhat.com> wrote: > > > ----- Original Message ----- > > > However, I briefly looked through the L2 agent code and didn't see a > > > periodic task to resync the port information to protect from a neutron > > > server that failed to send a notification because it crashed or lost > its > > > amqp connection. The L3 agent has a period sync routers task that > helps in > > > this regard. > > The L3 agent periodic sync is only if the full_sync flag was turned on, > which > is a result of an error. > > > > Maybe another neutron developer more familiar with the L2 > > > agent can chime in here if I'm missing anything. > > > > i don't think you are missing anything. > > periodic sync would be a good improvement. > > > > YAMAMAOTO Takashi > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150312/92c67962/attachment.html>