rabbit_lager: Multiply high watermark by 100 when log level is debug

[dumbbell]

Otherwise debug messages are quickly dropped by Lager.

[lukebakken]

Will this have an effect when the log level is debug from the start?

[lukebakken]

What do you think of 13f4117 ?

[michaelklishin]

When the node starts with debug level, it now uses the HWM value of 5000. That's fine.
If I then set log level to debug with

rabbitmqctl set_log_level debug

the value is bumped to 500K. Setting it to info after that with

rabbitmqctl set_log_level info

sets the value back to 5000 instead of 50.

[dumbbell]

Hmm when I start the node with the log level set to debug, the lager application env. still has a high watermark of 50 for me. I used the new config format.

@michaelklishin: how did you configure the initial log level?

[lukebakken]

I see what @dumbbell describes. HWM is 50 to start, then running set_log_level debug increases it to 5000. Running set_log_level info sets it back to 50.

Config file is as follows:

$ cat ~/issues/misc/rabbitmq.conf 
# Logging
log.console = true
log.console.level = debug
log.file.level = debug

[michaelklishin]

I start a node with gmake run-broker, that's it. No custom config file involved.

[michaelklishin]

It works as expected with an explicitly provided config. Could be something specific to my environment.

[lukebakken]

@michaelklishin I'm just now testing withmake run-broker and I see something similar to what you report. I'm investigating.

[lukebakken]

False alarm, run-broker is affected by this change: rabbitmq/rabbitmq-common@c049442

[michaelklishin]

With this PR I suggest that rabbitmq/rabbitmq-common@c049442 is reverted.

[dumbbell]

Thank you! I will take care of reverting the change in rabbitmq-common.

[dumbbell]

The problem with the initial patch is that setting the log level from the configuration does not change the high watermark on startup if that level is set to debug. I prepared another patch to help with this, so we can revert the change in rabbitmq-common.