Bug 1378383

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

Description of problem:

When a consumer of libgfapi users glfs_set_logging() to set a log level value, the expectation is that log level for gluster would be set to that value. However the logs from gluster behave as if they are set to the default loglevel i.e. GF_LOG_INFO despite the api returning SUCCESS.


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


How reproducible: always


Steps to Reproduce:
1.Alter the gluster log level of a gfapi consumer using glfs_set_logging() to a value other than GF_LOG_INFO.

2. Observe the logs from gluster

Actual results:

All logs upto level GF_LOG_INFO are seen


Expected results:

Only logs pertaining to the appropriate level should be seen from gluster


COMMIT: http://review.gluster.org/15112 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 5ce748ca45c6f2f867819400f50c9cdc12604226
Author: Vijay Bellur <vbellur>
Date:   Mon Aug 8 13:11:29 2016 -0400

    logging: Avoid re-initing log level in io-stats
    
    If log level is already set via api or command line, initialization of
    io-stats xlator overwrites the log level to GF_LOG_INFO. This patch
    prevents re-initialization of log level if already set.
    
    Change-Id: I1f74d94ef8068b95ec696638c0a8b17d8d71aabe
    BUG: 1368882
    Signed-off-by: Vijay Bellur <vbellur>
    Reported-by: Colin Lord <clord>
    Reviewed-on: http://review.gluster.org/15112
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>