Hi Anil,

Referring to the comments of jira 
https://jira.opendaylight.org/browse/OPNFLWPLUG-1060

We have received two events for the same flow-id in below order.
ADD event:           ADD flow with priority = 9

UPDATE event :   DELETE flow with priority = 9

                              ADD flow with priority = 6.


But the UPDATE event is processed first before ADD event.
Which is first trying to DELETE flow which doesn't exist followed by adding 
both the flows, though we received DataTreeChangeNotification in proper order.

Earlier we were handling flow mod requests in JobQueueHandler of 
NodeConfiguratorImpl, which was ensuring ordered processing.
With recent changes, we are using 
org.opendaylight.yangtools.util.concurrent.QueuedNotificationManager for 
request queue handling, which in this case is not ensuring the order.

Regards,
Somashekhar





_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to