Bug 1426115 - Add an ability to configure inactivity_probe for OVS
Summary: Add an ability to configure inactivity_probe for OVS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opendaylight
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 10.0 (Newton)
Assignee: Sridhar Gaddam
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-23 08:50 UTC by Sridhar Gaddam
Modified: 2018-10-18 07:25 UTC (History)
3 users (show)

Fixed In Version: opendaylight-5.2.0-6.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-03-23 16:15:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenDaylight Bug 7563 0 None None None 2017-02-23 08:50:40 UTC
OpenDaylight gerrit 51005 0 None None None 2017-02-23 08:51:40 UTC
Red Hat Product Errata RHBA-2017:0840 0 normal SHIPPED_LIVE opendaylight bug fix advisory 2017-03-23 20:14:35 UTC

Description Sridhar Gaddam 2017-02-23 08:50:40 UTC
Description of problem:
Echo request from OVS uses default value today, which is 5 seconds. In scale setups, Full GC can take more than 5 seconds which will result in a disconnection from all OVSs. In order to prevent that, configuring of inactivity_probe should be exposed by OVSDB.

Comment 1 Sridhar Gaddam 2017-02-23 08:51:41 UTC
Proposed the following downstream patch: https://code.engineering.redhat.com/gerrit/#/c/98243/

Comment 5 Itzik Brown 2017-03-12 08:35:12 UTC
Verified the following bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1426116
https://bugzilla.redhat.com/show_bug.cgi?id=1426119

Hence marking this one as verified.

Comment 7 errata-xmlrpc 2017-03-23 16:15:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0840.html


Note You need to log in before you can comment on or make changes to this bug.