[Bugs] [Bug 1356960] New: OOM Kill on client when heal is in progress on 1*3 arbiter volume

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1356960

            Bug ID: 1356960
           Summary: OOM Kill on client  when heal is in progress on 1*3
                    arbiter  volume
           Product: GlusterFS
           Version: mainline
         Component: arbiter
          Assignee: bugs at gluster.org
          Reporter: ksandha at redhat.com
                CC: bugs at gluster.org



Description of problem:
OOM kill led to unmount of the mount point when healling of the files in
progress.

Version-Release number of selected component (if applicable):
[root at dhcp43-157 guess]# gluster --version
glusterfs 3.9dev built on Jul 11 2016 10:04:54
Repository revision: git://git.gluster.com/glusterfs.git

How reproducible:
Hit once
BRICK1 DATA
BRICK2 DATA
BRICK3 ARBITER
Steps to Reproduce:
1. Create a 1*3 volume with arbiter - Volname GUESS
2. Mount the volume using fuse  /mnt/guesmount
3. create files using dd.sh 
for((i=1;i<=1000000;i++))
do 
dd if=/dev/urandom of=file$i bs=10K count=1
done
4. when the IO is started wait 5 mins ,kill brick process of B1
5. now after the script is over,  bring the B1 up using "gluster volume start
guess force"
6. Now kill the B3 brick and bring it up by  "gluster volume start guess force"


Observations:-
The heals were happening from B2 to B1 but when i killed the B3 brick. The
Heals started from B1 to B3. 

Actual results:
OOM kill was observed on the client with mount point inaccessible. 

Expected results:
No OOM kill should be observed

Additional info:
Logs are kept @
rhsqe-repo.lab.eng.blr.redhat.com:/var/www/html/sosreports/<bug>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.