Aha, you mean the API that OVSDB is using? That is more of a convenience and we can add without that too. I’ll add code for it. If needed, we can add util accordingly to OVSDB. Either ways, the fix

Hi, So it seems there should be 2 bugs? OVSDB needs to expose this in its addBridge interface and NETVIRT should allow to configure it. I couldn’t find how to configure it in

HI Guy, If this knob is needed for Controller’s probe timer bug should be on netvirt as netvirt is adding controller. In case of Manager, it should be set by whosoever configures manager, which

https://bugs.opendaylight.org/show_bug.cgi?id=7563

Aha! I meant for Manager. This field is present in Manager and Controller both and I was specifically talking about Manager. For controller, we were also creating controller manually, not using the

When you’re saying initial configuration do you mean before the OVS established an openflow connection? Configuration for Controller Table in OVSDB is being set by ODL. The CLI configuration for

We don’t have configuration for this today. We can add it or change netvirt code to add API. We changed it directly on OVS as part of initial configuration. We were using scripts to configure OVSes

Can we set this value via OVSDB configuration file? Or do we need to change code to use some api for this? Thanks

Close, inactivity_probe. Sorry for delay, had to fish in old logs.

Never mind, I found it, inactivity_probe Explanation here:http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf

max_backoff ?

Great thanks. Do you recall where you tweak this configuration ? A quick google search didn’t help me.

Good catch Anil. I forgot that we *did* increased timeout to 30-60 seconds from default of 5. I say 30-60 because we did different testing to reduce no. of echo messages going back and forth. But with

Hi Anil, In context of Openflowplugin (Helium) tests, we have observed this behavior when there is heavy GC induced due to immutables created and garbaged as part of flow provisioning combined

Full GC in a 8G-16G Heap takes about 10+ seconds

I think we should look at why OVS is getting disconnected during the GC? Is it because of the Echo timeout? Tuning GC will help, but i don't think so it will fix the root cause. I think if we can

Hi guys, So a couple of questions: 1) Did you reached Full GC? And if so, did the OVSs disconnected? And did everything continued working smoothly afterwards? 2) Do you have some

Hi Muthu, Yeah, we had used similar heap and GC settings when testing ITM which added OVSDB and all the netvirt models to the mix, I couldn’t recall what exactly were those.

Hi Vishal, We had focused mainly on baseline feature of OFPlugin so some of our changes specific to that drive-test may not be applicable for Guy’s case. However, increasing the Heap and using

Adding Muthu. Muthu, I believe we did have to do some tweaks with heapsize, GC settings etc.right? Do you recall? Regards, Vishal.