glusterfs/xlators/debug
Mohit Agrawal d2de3f6639 core: Log level changes do not effect on running client process
Problem: commit c34e4161f3 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
> (Cherry picked from commit 798aadbe51a9a02dd98a0f861cc239ecf7c8ed57)
> (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22495/)

Change-Id: If91682830f894ab8f6857f19dcb1797fc15ca64c
Fixes: bz#1699715
Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
2019-04-16 10:59:36 +00:00
..
delay-gen xlator: make 'xlator_api' mandatory 2018-12-13 14:41:50 +05:30
error-gen Don't depend on string options to be valid always 2018-12-17 17:19:00 +00:00
io-stats core: Log level changes do not effect on running client process 2019-04-16 10:59:36 +00:00
sink xlator: make 'xlator_api' mandatory 2018-12-13 14:41:50 +05:30
trace xlator: make 'xlator_api' mandatory 2018-12-13 14:41:50 +05:30
Makefile.am debug/delay-gen: Implement delay-generation feature 2017-08-31 17:17:09 +00:00