Bug 1546188 - api server get stuck after exhausting all grpc connections
Summary: api server get stuck after exhausting all grpc connections
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.9.0
Assignee: Stefan Schimanski
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-16 14:36 UTC by Michal Fojtik
Modified: 2018-03-28 14:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-28 14:29:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/deb/pprof/goroutine?debug=1 (286.26 KB, text/plain)
2018-02-16 15:09 UTC, Eric Paris
no flags Details
/metrics snapshot (6.06 MB, text/plain)
2018-02-16 15:22 UTC, Eric Paris
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:29:53 UTC

Description Michal Fojtik 2018-02-16 14:36:18 UTC
Description of problem:

Discovered during 3.9 upgrade in ca-centra-1 cluster. Seems like the gprc connections are not freed which will cause the api server to be stuck and eventually
have to be killed and restarted.

David made a monitoring tool that will detect this situation and automatically
panic the api server which force it to restart.

We need to figure out what is the root cause of this. It sounds like a race condition in gprc library.

Comment 5 Eric Paris 2018-02-16 15:09:37 UTC
Created attachment 1397069 [details]
/deb/pprof/goroutine?debug=1

Comment 6 Eric Paris 2018-02-16 15:22:19 UTC
Created attachment 1397085 [details]
/metrics snapshot

Comment 9 Derek Carr 2018-02-28 13:07:03 UTC
linked pr has merged.

Comment 17 errata-xmlrpc 2018-03-28 14:29:21 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-2018:0489


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