From e399f0f5b4661ac71bcf4f8badcd04d73b71a640 Mon Sep 17 00:00:00 2001
From: Gusted <williamzijl7@hotmail.com>
Date: Thu, 16 Jun 2022 11:10:33 +0200
Subject: [PATCH] Don't buffer doctor logger (#19982)
- We don't need to buffer the logger with a thousand capacity. It's not
a high-throughput logger, this also caused issue whereby the logger
can't keep up with repeated messages being send(somehow they are lost in
the queue?).
- Resolves #19969
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
---
cmd/doctor.go | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/doctor.go b/cmd/doctor.go
index 73dfeb1dbe9..3f16c6e2a60 100644
--- a/cmd/doctor.go
+++ b/cmd/doctor.go
@@ -203,7 +203,7 @@ func runDoctor(ctx *cli.Context) error {
// Now we can set up our own logger to return information about what the doctor is doing
if err := log.NewNamedLogger("doctorouter",
- 1000,
+ 0,
"console",
"console",
fmt.Sprintf(`{"level":"INFO","stacktracelevel":"NONE","colorize":%t,"flags":-1}`, colorize)); err != nil {