[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1463831 Title: neutron DVR poor performance Status in neutron: Expired Bug description: Scenario: 2 VMs of same tenant but in different subnets talk to each other. The traffic flow is ... Traffic VM1 to VM2: ========= CN1 ==================== ======== CN2 =========== VM1--->br-int--->Router--->br-int--->br-tun---------->br-tun--->br-int--->VM2 Traffic VM2 to VM1: ========= CN2 ==================== ======== CN1 =========== VM2--->br-int--->Router--->br-int---br-tun----------->br-tun--->br-int--->VM1 This works as designed; however obviously br-int of CN1 never gets traffic from Router of CN1 (except the very first ARP response), same for br-int of CN2. This might lead to flow (or mac?) timeout on br-int after 300 secs and degrades performance massively because traffic is flooded. Changing the mac-addr aging timer influences the issue; change to 30 (default 300) and the issue occurs after 30 seconds (instead 300) #ovs-vsctl set bridge br-int other_config:mac-aging-time=30 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1463831/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp