Maybe it is related to this: https://bugs.opendaylight.org/show_bug.cgi?id=6064
This issue started a like a week ago and is still pending for patch review. BR/Luis > On Jun 15, 2016, at 11:04 AM, Jamo Luhrsen <[email protected]> wrote: > > Adding openflowplugin-dev. > > I know there was some scale/perf work done recently as we released Beryllium, > so maybe one of those tests saw something like this. The description seems > like some kind of bug (although could be an OVS bug, ODL bug, or even test > bug) > > JamO > > > On 06/15/2016 07:28 AM, Georgiopoulos Panagiotis wrote: >> Hello, >> >> Recently we were experimenting with installing flows from the NorthBound >> interface to a topology of Mininet switches (OVS >> version 2.3.2). After sending a number of flows, we were checking for their >> existence in both the controller’s Operational >> DataStore and the topology switches. In some cases we observed that, even >> though the OpDS contained the intended number of >> flows, the switches had more than that number in total (usually, an extra >> number of flows almost equal to the number of >> switches). Empirically, this issue is observed when the flows-per-switch >> ratio is around 1000 or more (e.g. 30000 flows >> evenly distributed on 30 switches, etc.), while for lower ratios (e.g. 500 >> or 600) things work as expected, with both the >> OpDS and the switches containing the same, expected number of flows. >> >> Due to the scale of the number of flows and the different flow storage >> formats used in the OpDS and OVS, we were unable to >> dump and compare the flows to identify the extra ones. >> >> Have you ever observed such an issue in your tests? Any idea would be >> helpful. >> >> Best regards >> Panagiotis >> >> >> -- >> The information in this e-mail message and any attachments are intended only >> for the individual or entity to whom it is addressed and may be >> confidential. If you have received this transmission in error, and you are >> not an intended recipient, be aware that any copying, disclosure, >> distribution or use of this transmission or its contents is prohibited. >> INTRACOM TELECOM and the sender accept no liability for any loss, disruption >> or damage to your data or computer system that may occur while using data >> contained in, or transmitted with, this email. Views or opinions expressed >> in this message may be those of the author and may not necessarily represent >> those of INTRACOM TELECOM >> >> >> >> _______________________________________________ >> integration-dev mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/integration-dev >> > _______________________________________________ > integration-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
