[Bugs] [Bug 1294675] New: Healing queue rarely empty

[bugzilla at redhat.com]

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

            Bug ID: 1294675
           Summary: Healing queue rarely empty
           Product: GlusterFS
           Version: 3.7.6
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: nicolas at ecarnot.net
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
>From the command line of each host, and now constantly monitored by our
Nagios/Centreon setup, we see that our 3 nodes replica-3 gluster storage volume
is very frequently healing files, not to say constantly.

Version-Release number of selected component (if applicable):
Our setup : 3 Centos 7.2 nodes, with gluster 3.7.6 in replica-3, used as
storage+compute for an oVirt 3.5.6 DC.

How reproducible:
Install an oVirt setup on 3 nodes with glusterFS as direct gluster storage.
We have only 3 VMs running on it, so approx not more than 8 files (yes : only 8
files - the VM qemu files).

Steps to Reproduce:
1. Just run it and watch : all is nice
2. Run "gluster volume heal some_vol info" on random nodes
3. Read that more than zero files are getting healed

Actual results:
More than zero files are getting healed

Expected results:
I expected the "Number of entries" of every node to appear in the graph as a
flat zero line, most of the times, except for the rare cases of node reboot,
after which healing is launched and takes some minutes (sometimes hours) but is
doing good. 

Additional info:
At first, I found out that I forgot to bump up the cluster.op-version, but this
has been done, everything rebooted and back to up.
But this DC is very lightly used, and I'm sure the gluster clients (that are
the gluster nodes themselves) should read and write in a synchronous and proper
way, not leading to any healing need.

Please see :
https://www.mail-archive.com/gluster-users@gluster.org/msg22890.html

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