[Bugs] [Bug 1374606] New: geo-replication *changes.log does not respect the log-level configured

[bugzilla at redhat.com]

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

            Bug ID: 1374606
           Summary: geo-replication *changes.log does not respect the
                    log-level configured
           Product: GlusterFS
           Version: 3.7.15
         Component: geo-replication
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    csaba at redhat.com, rhs-bugs at redhat.com,
                    rnalakka at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1363729, 1363965



+++ This bug was initially created as a clone of Bug #1363965 +++

+++ This bug was initially created as a clone of Bug #1363729 +++

Description of problem:

Geo-replication *changes.log does not respect the log-level configured. Always
logs the trace &  debug logs regardless of the log-level configured. 


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

How reproducible:

Always

Steps to Reproduce:

1. Setup geo-replication session 
2. check the *changes.log under /var/log/glusterfs/geo-replication/<volname>


Actual results:

*changes.log logs the debug and trace logs even the log-level is info

Expected results:

*changes.log should log messages with respect to the log-level set

Additional info:

--- Additional comment from Aravinda VK on 2016-08-03 08:48:17 EDT ---

As a workaround(If manually editing files are ok)

Edit /usr/libexec/glusterfs/python/syncdaemon/master.py in all master nodes.
Search for CHANGELOG_LOG_LEVEL. Change the value from 9 to 7.

After changes are complete, Stop and Start the Geo-rep session. Changes log
should start logging in INFO mode.

Patch sent to upstream to fix the issue.
http://review.gluster.org/15078

--- Additional comment from Vijay Bellur on 2016-08-04 03:31:31 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#2) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-08-08 03:10:39 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#3) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-08-09 04:56:09 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#4) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Vijay Bellur on 2016-08-09 06:54:55 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#5) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Worker Ant on 2016-08-22 01:21:31 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#6) for review on master by Atin Mukherjee
(amukherj at redhat.com)

--- Additional comment from Worker Ant on 2016-08-25 04:17:26 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#7) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Worker Ant on 2016-09-08 02:20:38 EDT ---

REVIEW: http://review.gluster.org/15078 (geo-rep: Use configured log_level for
libgfchangelog logs) posted (#8) for review on master by Aravinda VK
(avishwan at redhat.com)

--- Additional comment from Worker Ant on 2016-09-09 03:23:33 EDT ---

COMMIT: http://review.gluster.org/15078 committed in master by Aravinda VK
(avishwan at redhat.com) 
------
commit f41ec4fcfaa9ca976fddbe9e91aabf840c20111f
Author: Aravinda VK <avishwan at redhat.com>
Date:   Wed Aug 3 17:52:20 2016 +0530

    geo-rep: Use configured log_level for libgfchangelog logs

    libgfchangelog was not respecting the log_level configured
    in Geo-replication. With this patch Libgfchangelog log level
    can be configured using `config changelog_log_level TRACE`.
    Default Changelog log level is INFO

    BUG: 1363965
    Change-Id: Ida714931129f6a1331b9d0815da77efcb2b898e3
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/15078
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1363965
[Bug 1363965] geo-replication *changes.log does not respect the log-level
configured
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.