Hi Alex, That's cool! Just one more question. > Due to the race condition in userspace, there is chance that two > overlapping megaflows could be installed in datapath. And this > causes userspace unable to delete the less inclusive megaflow flow > even after it timeout, since the flow_del logic will stop at the > first match of masked flow.
Does it mean if the more inclusive megaflow (say A) is deleted, then the less inclusive megaflow (say B) can be deleted? If so, I can have a workaround without updating OVS version: I can find out the more inclusive megaflow and manually delete flows with ovs-dpctl in order (A -> B), then warning logs should stop, right? On Tue, Jul 1, 2014 at 5:36 AM, Alex Wang <al...@nicira.com> wrote: > Hey Han, > > We found the issue, fix has been sent here: > http://openvswitch.org/pipermail/dev/2014-June/042333.html > > Thanks again for reporting, > Alex Wang, > > > On Wed, Jun 11, 2014 at 3:54 AM, Han Zhou <zhou...@gmail.com> wrote: >> >> Hello folks, >> >> We encountered a problem on a hypervisor with OVS2.0, that there are >> warning logs flooding in ovs-vswitchd.log: >> >> 2014-06-10T13:25:11.761Z|15084062|dpif|WARN|Dropped 67 log messages in >> last 1 seconds (most recently, 1 seconds ago) due to excessive rate >> 2014-06-10T13:25:11.761Z|15084063|dpif|WARN|system@ovs-system: failed >> to flow_del (No such file or directory) ... >> >> This log is printed every 1 second. And the flow do exists on the >> hypervisor (shown by ovs-dpctl dump-flows). >> >> Could someone help explain the root cause, and suggest the actions to fix? >> >> Best regards, >> Han >> _______________________________________________ >> discuss mailing list >> discuss@openvswitch.org >> http://openvswitch.org/mailman/listinfo/discuss > > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
