Bug 1319332 - Memory overcommitted
Summary: Memory overcommitted
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Anoop
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 21:09 UTC by Fred Yang
Modified: 2018-02-07 04:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-07 04:20:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Fred Yang 2016-03-18 21:09:03 UTC
Description of problem:
Glusterfsd appears overcommited memory

Version-Release number of selected component (if applicable):
v3.7.6 / RHEL v6.6

How reproducible:
Glusterfsd ran for ~10 days and then seeing memory overcommitted

Steps to Reproduce:
Nothing special, just run glusterfsd for ~10 days. The cluster node has 24G RAM with 20 glusterfsd processes

Actual results:
/proc/meminfo:
 MemTotal:       24414040 kB
 MemFree:         1158296 kB
 Buffers:          405876 kB 
 Cached:         18039396 kB 
 ..
 CommitLimit:    20497320 kB
 Committed_AS:   44178840 kB
 VmallocTotal:   34359738367 kB 
 VmallocUsed:      630888 kB 
 VmallocChunk:   34344910868 kB 

Expected results:


Additional info:
Ran 'echo 2 > /proc/sys/vm/drop_caches' to drop the cache, MemFree increased:
 MemTotal:       24414040 kB
 MemFree:        18648448 kB
 Buffers:          436724 kB
 Cached:           673008 kB
But Committed_AS remain high:
 CommitLimit:    20497320 kB
 Committed_AS:   44178840 kB
 VmallocTotal:   34359738367 kB
 VmallocUsed:      630900 kB
 VmallocChunk:   34344910868 kB

Comment 2 Amar Tumballi 2018-02-07 04:20:02 UTC
Thank you for your report. This bug is filed against a component for which no further new development is being undertaken.

If you find the bug relevant in the higher versions too, please feel free to reopen the bug.


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