[Bugs] [Bug 1283956] New: Self-heal triggered every couple of seconds and a 3-node 1-arbiter setup

[bugzilla at redhat.com]

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

            Bug ID: 1283956
           Summary: Self-heal triggered every couple of seconds and a
                    3-node 1-arbiter setup
           Product: GlusterFS
           Version: 3.7.6
         Component: unclassified
          Assignee: bugs at gluster.org
          Reporter: adrian.gruntkowski at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

I have a 3 node setup with 1 arbiter brick for every volume. Every volume
contains a couple of big files with KVM disk images.

Every couple of minutes/seconds (probably depends on activity), a self-heal
operation is triggered on one or more files on the volumes. During that time,
there's no noticable loss of connectivity or anything like that.

How reproducible:

Run "gluster volume heal volume-name info" a couple of times and observe the
output.


Actual results:

root at web-vm:~# gluster volume heal system_www1 info
Brick cluster-rep:/GFS/system/www1
/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal

Number of entries: 1

Brick web-rep:/GFS/system/www1
/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal

Number of entries: 1

Brick mail-rep:/GFS/system/www1
/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal

Number of entries: 1

Expected results:

Heal not being triggered without a reason.

Additional info:

Setting "cluster.self-heal-daemon" to "off" on the volumes does not change the
behavior.

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