Bug 1420619

Description of problem:
=======================

This is a logging issue. After replace-brick, glustershd log shows entry heal successful messages while no entries are shown with heal info command. These are informatory messages.

[2015-11-17 09:09:17.262558] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.8/newfile.79: name heal successful on FFF
[2015-11-17 09:09:17.457770] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.8/newfile.80: name heal successful on FFF
[2015-11-17 09:09:17.597917] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.9/newfile.94: name heal successful on FFF
[2015-11-17 09:09:17.625835] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.8/newfile.81: name heal successful on FFF
[2015-11-17 09:09:18.067542] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.8/newfile.82: name heal successful on FFF
[2015-11-17 09:09:18.348196] I [MSGID: 122058] [ec-heal.c:2338:ec_heal_do] 0-vol1-disperse-0: /files/dir.9/newfile.95: name heal successful on FFF


Version-Release number of selected component (if applicable):
=============================================================
3.7.5-6

[root@transformers ~]# gluster --version
glusterfs 3.7.5 built on Nov 10 2015 00:13:38
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
=================
glustershd should show the entries only for the files which get healed.

Additional info:

REVIEW: https://review.gluster.org/16580 (cluster/ec: Change log level of messages to DEBUG) posted (#1) for review on master by Sunil Kumar Acharya (sheggodu)

REVIEW: https://review.gluster.org/16580 (cluster/ec: Change log level of messages to DEBUG) posted (#2) for review on master by Sunil Kumar Acharya (sheggodu)

REVIEW: https://review.gluster.org/16580 (cluster/ec: Change log level of messages to DEBUG) posted (#3) for review on master by Sunil Kumar Acharya (sheggodu)

REVIEW: https://review.gluster.org/16580 (cluster/ec: Change log level of messages to DEBUG) posted (#4) for review on master by Sunil Kumar Acharya (sheggodu)

COMMIT: https://review.gluster.org/16580 committed in master by Xavier Hernandez (xhernandez) 
------
commit a6ece44d0bbdecf38252f477b4aa98a76771a328
Author: Sunil Kumar Acharya <sheggodu>
Date:   Thu Feb 9 16:34:54 2017 +0530

    cluster/ec: Change log level of messages to DEBUG
    
    Heal failed or passed should not be logged as info. These can be
    observed from heal info if the heal is happening or not. If we require
    to debug a case where heal is not happening, we can set the level to
    DEBUG.
    
    Change-Id: I062668eadd145ef809b25e818e6bca1094f54cd6
    BUG: 1420619
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/16580
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Ashish Pandey <aspandey>

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/