From 798aadbe51a9a02dd98a0f861cc239ecf7c8ed57 Mon Sep 17 00:00:00 2001 From: Mohit Agrawal Date: Thu, 4 Apr 2019 09:56:11 +0530 Subject: core: Log level changes do not effect on running client process Problem: commit c34e4161f3cb6539ec83a9020f3d27eb4759a975 set log-level per xlator during reconfigure only for a brick process not for the client process. Solution: 1) Change per xlator log-level only if brick_mux is enabled.To make sure about brick multiplex introudce a flag brick_mux at ctx->cmd_args. Note: There are two other changes done with this patch 1) Ignore client-log-level option to attach a brick with already running brick if brick_mux is enabled 2) Add a log to print pid of the running process to make easier debugging Change-Id: I39e85de778e150d0685cd9a79425ce8b4783f9c9 Signed-off-by: Mohit Agrawal Fixes: bz#1696046 --- libglusterfs/src/glusterfs/glusterfs.h | 1 + 1 file changed, 1 insertion(+) (limited to 'libglusterfs') diff --git a/libglusterfs/src/glusterfs/glusterfs.h b/libglusterfs/src/glusterfs/glusterfs.h index cdb6d97eec1..4e5669c6dae 100644 --- a/libglusterfs/src/glusterfs/glusterfs.h +++ b/libglusterfs/src/glusterfs/glusterfs.h @@ -581,6 +581,7 @@ struct _cmd_args { int fuse_auto_inval; bool global_threading; + bool brick_mux; }; typedef struct _cmd_args cmd_args_t; -- cgit