Re: [ovsdb-dev] OVSDB scale
|
Vishal Thapar <vishal.thapar@...>
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 will be going in Netvirt, OVSDB change may or may not be needed.
Regards, Vishal.
From: Sela, Guy [mailto:guy.sela@...]
Sent: 17 January 2017 19:54 To: Vishal Thapar <vishal.thapar@...>; Pearl, Tomer <tomer.pearl@...>; Anil Vishnoi <vishnoianil@...> Cc: Muthukumaran K <muthukumaran.k@...>; Jamo Luhrsen <jluhrsen@...>; marcus.g.williams@...; openflowjava-dev@...; ovsdb-dev@... Subject: RE: [openflowjava-dev] [ovsdb-dev] OVSDB scale
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 OvsdbBridgeAugmentationBuilder and not in SouthboundUtils.addBridge
From: Vishal Thapar [mailto:vishal.thapar@...]
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 never comes from OVSDB.
Any configuration that goes into OVSDB in switch should ideally come from consumers of OVSDB, not plugin itself.
I can change this to netvirt bug, but want to make sure we are in agreement on nature of change coming in ie.e. a knob to set default inactivity for Controller that gets created by autobridge.
Regards, Vishal.
From: Sela, Guy [mailto:guy.sela@...]
https://bugs.opendaylight.org/show_bug.cgi?id=7563
From: Vishal Thapar [mailto:vishal.thapar@...]
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 autobridge code. I’d recommend creating an enhancement bug for this. We should add this knob and code to autobridge.
Regards, Vishal.
From: Sela, Guy [mailto:guy.sela@...]
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 the inactivity probe looks like this for example: sudo ovs-vsctl add Controller 8383a19f-4899-4808-ba0b-c970af081c3e inactivity_probe 10000
So it looks like this can only be set after the connection
From: Vishal Thapar [mailto:vishal.thapar@...]
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 with manager, so just added one more command. Another parameter you may want to look at is stats_interval which governs how frequently stat updates come, though we later on disabled stats by default.
Finally, if you’re using HA Proxy between OVS and ODL for manager connection or using single node i.e. OVS connects to only one manager at a time, you can tweak a flag captured in this: https://git.opendaylight.org/gerrit/#/c/49068/
If you change this for a deployment where each OVS connects to each ODL node in cluster [multiple manager connections to cluster] changing this flag can have functional impact, so be careful.
Regards, Vishal.
From: Pearl, Tomer [mailto:tomer.pearl@...]
Can we set this value via OVSDB configuration file? Or do we need to change code to use some api for this? Thanks
From: Vishal Thapar [mailto:vishal.thapar@...]
Close, inactivity_probe. Sorry for delay, had to fish in old logs.
From: Sela, Guy [mailto:guy.sela@...]
max_backoff ?
From: Sela, Guy
Great thanks. Do you recall where you tweak this configuration ? A quick google search didn’t help me.
From: Vishal Thapar [mailto:vishal.thapar@...]
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 5 we used to see frequent disconnects, so yes, I’d agree with Anil that increasing timeouts should be a better solution. In fact default of 5 is terrible as you start scaling up, you’ll be processing too many echo messages.
Regards, Vishal.
From: Sela, Guy [mailto:guy.sela@...]
Full GC in a 8G-16G Heap takes about 10+ seconds
From: Anil Vishnoi [mailto:vishnoianil@...]
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 increase the echo timeouts, probably disconnection won't happen atleast because of GC.
On Tue, Jan 17, 2017 at 1:15 AM, Sela, Guy <guy.sela@...> wrote:
-- Thanks Anil |