[openstack-dev] [neutron]OVS connection tracking cleanup

Kevin Benton kevin at benton.pub
Mon Sep 11 16:48:48 UTC 2017

The biggest improvement will be switching to native netlink calls:

How many VMs were on a single compute node?

On Mon, Sep 11, 2017 at 9:15 AM, Ajay Kalambur (akalambu) <
akalambu at cisco.com> wrote:

> Hi
> I am performing a scale test and I see that after creating 500 Vms with
> ping traffic between them it took almost 1 hr for the connection tracking
> To clean up and ovs agent was busy doing this and unable to service any
> new port bind requests on some computes for almost an hr
> It took that long for conntrack clean up to complete
> I see the following bug
> https://bugs.launchpad.net/neutron/+bug/1513765
> And I also have the fix below
> https://git.openstack.org/cgit/openstack/neutron/commit/?id=
> d7aeb8dd4b1d122e17eef8687192cd122b79fd6e
> Still see really long times for conntrack cleanup
> What is the solution to this problem in scale scenarios?
> Ajay
> __________________________________________________________________________
> 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/20170911/85c003a6/attachment.html>

More information about the OpenStack-dev mailing list