Bug 1427532

Summary: [3.5] Restarting atomic-openshift-master-api takes ~5 minutes to restart
Product: OpenShift Container Platform Reporter: Eric Paris <eparis>
Component: NodeAssignee: Derek Carr <decarr>
Status: CLOSED ERRATA QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.1CC: aos-bugs, dakini, decarr, dma, jgoulding, jokerman, mifiedle, mmccomas, mwhittin, tdawson
Target Milestone: ---Keywords: OpsBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: excessive logging to journal Consequence: caused masters to take longer to restart Fix: reduce the amount of logging that occurs when initial list/watch actions happen against etcd. Result: the journal is no longer pegged with a lot of messages that cause logging messages to be rate limited and dropped. server restart time should be improved on clusters with larger data sets.
Story Points: ---
Clone Of: 1425211 Environment:
Last Closed: 2017-04-12 19:14:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1425211    
Bug Blocks: 1303130    

Comment 1 Troy Dawson 2017-03-01 22:53:13 UTC
I'm declaring that this is the bug for 3.5.
This has been merged into ocp and is in OCP v3.5.0.37 or newer.

Comment 3 DeShuai Ma 2017-03-02 09:33:19 UTC
Verify on openshift v3.5.0.37. restart master works well and we don't meet this bugs after one days testing.
[root@ip-172-18-8-15 ~]# openshift version
openshift v3.5.0.37
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Comment 5 errata-xmlrpc 2017-04-12 19:14:06 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://access.redhat.com/errata/RHBA-2017:0884