Bug 1369382
Summary: | Glusterd mem leak when run command gluster volume status | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Yu.Changcai <einstcrazy> |
Component: | glusterd | Assignee: | Gaurav Yadav <gyadav> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | amukherj, bugs, kaushal |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-07 10:43:37 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: |
Description
Yu.Changcai
2016-08-23 09:14:27 UTC
GlusterFS-3.6 is nearing its End-Of-Life, only important security bugs still make a chance on getting fixed. Moving this to the mainline 'version'. If this needs to get fixed in 3.7 or 3.8 this bug should get cloned. I try to reproduce the issue, but after multiple trials issue is not being reproduced.. I have used mainline build for my testing. Reproduction steps. 1. Create a 2 node cluster 2. Create volume with 3 bricks on both the nodes. 3. Start the volume. 4. Execute the command gluster volume status in a script for 1 hr, 5. Monitor memory of glusterd process. I didn't see memory is increasing for glusterd process when gluster v status command ie being executed. As issue is not getting reproduced in mainline, closing the bug. |