-
Bug
-
Resolution: Duplicate
-
None
-
None
-
None
-
Operating System: Linux
Platform: All
-
8458
I ran the following performance tests using ODL Boron-SR3 and OVS 2.5.0:
when the switch is connected to ODL, I use the SAL Flow API to send 10000 flows as fast as possible to the switch.
The flows are all of the following types:
cookie=0x0, duration=6.411s, table=0, n_packets=0, n_bytes=0, idle_age=6, priority=0, tcp, nw_src=10.0.0.1, nw_dst=10.0.0.2, tp_src=1346, tp_dst=80 actions=CONTROLLER:65535,output:1
and I increment the tp_src field for each flow.
Problem: before the 10000 flows are installed, ODL disconnects from OVS with the following errors:
No queue present, failing request
And the futures returned by salFlowService.addFlow show the following error message:
Error: [operation-failed]: Device disconnected
The OVS logs shows the following message:
2017-05-15T15:37:48.808Z|02743|rconn|ERR|s1<->tcp:127.0.0.1:6633: no response to inactivity probe after 5 seconds, disconnecting
Thanks
Thomas
- duplicates
-
OPNFLWPLUG-918 Regression: Controller fails to delete 100K flows from switches
- Confirmed