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

[bugzilla at redhat.com]

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

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



+++ 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

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