Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1243886 - huge mem leak in posix xattrop [NEEDINFO]
huge mem leak in posix xattrop
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.1.1
Assigned To: Vijaikumar Mallikarjuna
Bhaskarakiran
: ZStream
Depends On:
Blocks: 1243890 1243898 1251815
  Show dependency treegraph
 
Reported: 2015-07-16 09:58 EDT by Vijaikumar Mallikarjuna
Modified: 2016-11-23 18:11 EST (History)
13 users (show)

See Also:
Fixed In Version: glusterfs-3.7.1-12
Doc Type: Bug Fix
Doc Text:
Previously, there was a huge memory leak in bricks and it consumed huge memory. With this fix, this issue is resolved.
Story Points: ---
Clone Of:
: 1243890 (view as bug list)
Environment:
Last Closed: 2015-10-05 03:20:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bsrirama: needinfo? (vmallika)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1845 normal SHIPPED_LIVE Moderate: Red Hat Gluster Storage 3.1 update 2015-10-05 07:06:22 EDT

  None (edit)
Description Vijaikumar Mallikarjuna 2015-07-16 09:58:28 EDT
There is a huge memory leak in xattrop.
marker xlator uses xattrop for every txn, this can cause brick process to consume huge memory because because of leak in xattrop where array is not freed
Comment 6 Byreddy 2015-09-01 02:37:15 EDT
Vijai,

Pls want to know the steps to verify this bug from QA end.

Thanks
Comment 7 Bhaskarakiran 2015-09-02 01:43:48 EDT
Ran the same workload which showed up memory leak in bricks. Didn't see any issue. Moving this to verified.
Comment 9 errata-xmlrpc 2015-10-05 03:20:48 EDT
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-2015-1845.html

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