diff options
author | Mohit Agrawal <moagrawal@redhat.com> | 2019-04-04 09:56:11 +0530 |
---|---|---|
committer | Atin Mukherjee <amukherj@redhat.com> | 2019-04-15 04:30:43 +0000 |
commit | 798aadbe51a9a02dd98a0f861cc239ecf7c8ed57 (patch) | |
tree | 492c9d756bdacfbeb7db8f0ce975d33c99e01097 /libglusterfs/src/glusterfs/latency.h | |
parent | a67929e18a39d5c79a4a7e2b78015523626a367e (diff) |
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 <moagrawal@redhat.com>
Fixes: bz#1696046
Diffstat (limited to 'libglusterfs/src/glusterfs/latency.h')
0 files changed, 0 insertions, 0 deletions