RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1446184 - dockerd hangs if a EventMemberJoin is received while joining a Node found in KV store
Summary: dockerd hangs if a EventMemberJoin is received while joining a Node found in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1298243
TreeView+ depends on / blocked
 
Reported: 2017-04-27 12:12 UTC by Sergio Lopez
Modified: 2020-06-11 13:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Their was a race condition where the docker daemon could hang under load. This version fixes this race condition.
Clone Of:
Environment:
Last Closed: 2017-05-26 14:52:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Hung dockerd core file generated by gcore (2.76 MB, application/x-gzip)
2017-04-27 12:12 UTC, Sergio Lopez
no flags Details
Backtrace from all goroutines of hung dockerd (213.14 KB, text/plain)
2017-04-27 12:14 UTC, Sergio Lopez
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1325 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2017-05-26 18:14:24 UTC

Description Sergio Lopez 2017-04-27 12:12:15 UTC
Created attachment 1274607 [details]
Hung dockerd core file generated by gcore

Description of problem:

On a Docker environment with Cluster Store, Cluster Advertise, and some Overlay networks, if an EventMemberJoin event is received while processing a Node found in KV store, dockerd process hangs indefinitely.


Version-Release number of selected component (if applicable):

Tested with docker-1.12.6-11.el7.x86_64


How reproducible:

Sometimes, depends on Nodes coordination.


Steps to Reproduce:
1. Prepare a 3 node Docker environment with Cluster Store and Cluster Advertise.
2. Create some Overlay Networks.
3. Create a few containers with an automatic restart policy.
4. Restart dockerd a few times.


Actual results:

dockerd becomes unresponsive (service socket is created, but doesn't answer to connection requests).


Expected results:

dockerd shouldn't hang.


Additional info:

The root cause is that peerDbNetworkWalk iterates through the map calling the passed function while holding pMap.Lock. One of the functions passed to peerDbNetworkWalk is pushLocalEndpointEvent, which sends an event to the serf channel.

Meanwhile, if an EventMemberJoin event has been received by ov_serf event channel, it will eventually call peerAdd, which tries to hold the same pMap.Lock.

So we have startSerfLoop busy waiting for pMap.Lock to be released, and peerDbNetworkWalk holding the lock while waiting in pushLocalEndpointEvent, causing the deadlock.

This has been addressed upstream by this commit: https://github.com/docker/libnetwork/commit/760abd041b3100007987423140db1f169c84dab9

Comment 2 Sergio Lopez 2017-04-27 12:14:42 UTC
Created attachment 1274608 [details]
Backtrace from all goroutines of hung dockerd

Comment 3 Sergio Lopez 2017-04-27 12:18:54 UTC
docker-1.12.6-16 from RHEL 7.3 is also affected since Project Atomic's libnetwork commit level is behind upstream.

Comment 4 Antonio Murdaca 2017-04-27 12:42:06 UTC
Fixed in docker-1.12.6 via https://github.com/projectatomic/docker/commit/c14458a6b1955fc2a6793eea297b43821837285a

Comment 5 Antonio Murdaca 2017-04-27 12:47:38 UTC
Fixed in docker-1.13.1 as well, FYI

Comment 8 errata-xmlrpc 2017-05-26 14:52:04 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:1325


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