Description of problem: logging: Fix per xl log level. Currently per xlator loglevel setting doesn't work, due to the flaw in loglevel checking. Fix the same. Per xlator logging can be set using the below command: Eg: setfattr -n trusted.glusterfs.patchy-md-cache.set-log-level -v TRACE /mnt/glusterfs/0 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15071 (logging: Fix per xl log level) posted (#2) for review on master by Poornima G (pgurusid)
REVIEW: http://review.gluster.org/15071 (logging: Fix per xl log level) posted (#3) for review on master by Poornima G (pgurusid)
REVIEW: http://review.gluster.org/15071 (logging: Fix per xl log level) posted (#4) for review on master by Poornima G (pgurusid)
COMMIT: http://review.gluster.org/15071 committed in master by Jeff Darcy (jdarcy) ------ commit 206fd324e33127d4c370007f223f8c12ab06b714 Author: Poornima G <pgurusid> Date: Tue Aug 2 16:17:36 2016 +0530 logging: Fix per xl log level Currently per xlator loglevel setting doesn't work, due to the flaw in loglevel checking. Fix the same. Per xlator logging can be set using the below command: Eg: setfattr -n trusted.glusterfs.patchy-md-cache.set-log-level -v TRACE /mnt/glusterfs/0 Change-Id: I8ff1d15bd5693b6f682d99bee22a4bbb5eee646c BUG: 1362520 Signed-off-by: Poornima G <pgurusid> Reviewed-on: http://review.gluster.org/15071 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jeff Darcy <jdarcy>
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.9.0, please open a new bug report. glusterfs-3.9.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/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/