From 6e17fb2097f941798e1d56728fd3d61e525a39a5 Mon Sep 17 00:00:00 2001 From: Gaurav Kumar Garg Date: Wed, 12 Aug 2015 01:09:41 +0530 Subject: glusterd: DEBUG log should not come after resetting client log level After resetting diagnostics.client-log-level option still DEBUG log is logging in scrubber and bitrot log file. After resetting any option value of that options goes to default value. This patch will set the default value of client and brick log level to "INFO" log level. Change-Id: I4cf04754dcf5ddc908dae4d9bdf525cfcd6cc2bd BUG: 1252696 Signed-off-by: Gaurav Kumar Garg Reviewed-on: http://review.gluster.org/11887 Tested-by: NetBSD Build System Tested-by: Gluster Build System Reviewed-by: Atin Mukherjee --- xlators/mgmt/glusterd/src/glusterd-volume-set.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'xlators/mgmt/glusterd/src') diff --git a/xlators/mgmt/glusterd/src/glusterd-volume-set.c b/xlators/mgmt/glusterd/src/glusterd-volume-set.c index cbda00250e1..e4765f6f0d9 100644 --- a/xlators/mgmt/glusterd/src/glusterd-volume-set.c +++ b/xlators/mgmt/glusterd/src/glusterd-volume-set.c @@ -1037,11 +1037,13 @@ struct volopt_map_entry glusterd_volopt_map[] = { }, { .key = "diagnostics.brick-log-level", .voltype = "debug/io-stats", + .value = "INFO", .option = "!brick-log-level", .op_version = 1 }, { .key = "diagnostics.client-log-level", .voltype = "debug/io-stats", + .value = "INFO", .option = "!client-log-level", .op_version = 1, .flags = OPT_FLAG_CLIENT_OPT -- cgit