Description of problem: ====================== It would be really helpful for debugging any issues related to glusterd if we can set the log level of glusterd using a command rather than restarting the glusterd with "DEBUG" option. If we restart the glusterd, we might not hit the issue after restart as we lose the current state of glusterd. . Hence it would be really helpful to have a option to set the glusterd log levels. For example: https://bugzilla.redhat.com/show_bug.cgi?id=1121015 doesn't have enough information in the glusterd logs on why the command failed. The developer wants more information but we are get the information without restarting glusterd. Version-Release number of selected component (if applicable): ============================================================ glusterfs 3.6.0.24 built on Jul 3 2014 11:03:38
Are you looking at a command to set a specific log level per glusterd or cli command should set the log level of glusterd across the cluster?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days