Hey Han, Thanks for pointing this out,
Please see my reply inline, On Wed, Jun 11, 2014 at 9:40 PM, Han Zhou <zhou...@gmail.com> wrote: > Hi Alex, > > I see that you encountered this error log before in your tests. Is > this a bug that's already fixed? Could you help explain and give > advice how to clean up (this is a production hypervisor and no plan to > upgrade at this moment)? > > The issue I encountered is for ovs-2.1 and later when we start dumping flows from datapath periodically. Basically, the warning log means that the ovs tries to delete a non-existent flow in datapath. > Note: this is OVS2.0. It seems OVS is retrying deleting 1 entry for 10 > minutes and switch to next one. There are about 60+ such "zombie" > entries in the datapath flow table which never gets deleted and > results in the warning logs flooding. > > For OVS-2.0, we still use facet and subfacet in ofproto-dpif to keeps record of the flows. And the flow revalidation logic is quite different from later branches. So, the fix in later branches does not apply here. What you saw likely indicates the following scenario: e.g. a datapath flow could be dumped -> but ovs could not find corresponding subfacet (due to bug) -> so, ovs deleted the datapath flow -> later when the subfacet is to be deleted, it tries deleting the datapath flow -> but the datapath flow does not exist and you saw the warning in log. But, it surprised me that you saw 60+ flows in datapath that should be deleted. Did those 'Zombie' flows get hit? Could you provide more info about how to reproduce it? Thanks, Alex Wang,
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
