Bug 1343320
Summary: | [GSS] Gluster fuse client crashed generating core dump | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Bipin Kunal <bkunal> | |
Component: | fuse | Assignee: | Nithya Balachandran <nbalacha> | |
Status: | CLOSED ERRATA | QA Contact: | Prasad Desala <tdesala> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | rhgs-3.1 | CC: | amukherj, csaba, lasilva, nbalacha, rcyriac, rfreire, rgowdapp, rhinduja, smohan | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.2.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | dht-qe-3.2, dht-gss, dht-gss-ask, dht-3.2.0-proposed | |||
Fixed In Version: | glusterfs-3.8.4-1 | Doc Type: | Bug Fix | |
Doc Text: |
After a connection failure, the Gluster FUSE client did not correctly clean up threads spawned to handle the failure, which resulted in a memory leak. This caused a crash when the process was killed to reclaim memory. Threads are now cleaned up correctly and the process is no longer killed, preventing the crash.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1343374 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-23 05:34:56 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: | ||||
Bug Blocks: | 1343374, 1351515, 1351530, 1354250, 1360553 |
Description
Bipin Kunal
2016-06-07 06:58:18 UTC
Upstream patch available at: http://review.gluster.org/#/c/14661/ Upstream mainline : http://review.gluster.org/14875 Upstream 3.8 : http://review.gluster.org/14979 And the fix is available in rhgs-3.2.0 as part of rebase to GlusterFS 3.8.4. Followed the same steps updated in Comment 11 on a 3.1.3 system. I am able to see continuous "DNS resolution failed" errors in the fuse logs and the memory usage keeps growing which results the system to crash. Same steps were followed to verify this BZ on a 3.8.4-2.el7rhgs.x86_64 system. After the fix, no memory leak is seen due to the "DNS resolution failed" errors. Hence, moving this BZ to Verified. Looks good. Thanks Laura. 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/RHSA-2017-0486.html |