Bug 1427532 - [3.5] Restarting atomic-openshift-master-api takes ~5 minutes to restart
Summary: [3.5] Restarting atomic-openshift-master-api takes ~5 minutes to restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On: 1425211
Blocks: OSOPS_V3
TreeView+ depends on / blocked
 
Reported: 2017-02-28 14:23 UTC by Eric Paris
Modified: 2017-07-24 14:11 UTC (History)
10 users (show)

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.
Clone Of: 1425211
Environment:
Last Closed: 2017-04-12 19:14:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ose pull 629 0 None None None 2017-02-28 14:25:10 UTC
Red Hat Product Errata RHBA-2017:0884 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 22:50:07 UTC

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
Note You need to log in before you can comment on or make changes to this bug.