[Bugs] [Bug 1201203] New: glusterd OOM killed, when repeating volume set operation in a loop
bugzilla at redhat.com
bugzilla at redhat.com
Thu Mar 12 10:11:20 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1201203
Bug ID: 1201203
Summary: glusterd OOM killed, when repeating volume set
operation in a loop
Product: GlusterFS
Version: mainline
Component: core
Severity: high
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
nlevinki at redhat.com, rhs-bugs at redhat.com,
sasundar at redhat.com, vbellur at redhat.com
Depends On: 1198968
+++ This bug was initially created as a clone of Bug #1198968 +++
Description of problem:
-----------------------
While repeating volume set operation in the loop, glusterd gets OOM killed
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Mainline
How reproducible:
-----------------
Consistent
Steps to Reproduce:
-------------------
1. Create a 2 node 'Trusted Storage Pool' ( cluster )
2. Create 2 distribute volumes with 2 bricks ( 1 brick per node ) and start it
3. From NODE1, in one loop, keep repeating 'volume set' on one volume (say
vol1)
4. Frome NODE2, in other loop, keep repeating 'volume set' on other volume (
say vol2 )
Actual results:
---------------
After an hour, glusterd got OOM killed.
Expected results:
-----------------
glusterd should get OOM Killed
--- Additional comment from SATHEESARAN on 2015-03-05 04:10:11 EST ---
glusterd statedump file while the memory consumption was high enough.
This was taken 10 minutes before glusterd got OOM Killed
--- Additional comment from SATHEESARAN on 2015-03-05 04:12:52 EST ---
sosreport as taken from NODE1, where the glusterd got OOM killed
--- Additional comment from SATHEESARAN on 2015-03-05 04:16:54 EST ---
Reproducible test case1 :
--------------------------
0. Create a 2 node cluster
1. Create a distribute volume and start it.
2. Create a shell script as follows :
while true; do gluster volume set <vol-name1> read-ahead on; done
3. Run the above script in the background.
4. From RHSS command line execute the following,
while true; do gluster volume set <vol-name2> write-behind on; done
5. Monitor the memory consumed by glusterd
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1198968
[Bug 1198968] glusterd OOM killed, when repeating volume set operation in a
loop
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list