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>
This commit is contained in:
parent
b01dce2a6e
commit
e399f0f5b4
|
@ -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
|
// Now we can set up our own logger to return information about what the doctor is doing
|
||||||
if err := log.NewNamedLogger("doctorouter",
|
if err := log.NewNamedLogger("doctorouter",
|
||||||
1000,
|
0,
|
||||||
"console",
|
"console",
|
||||||
"console",
|
"console",
|
||||||
fmt.Sprintf(`{"level":"INFO","stacktracelevel":"NONE","colorize":%t,"flags":-1}`, colorize)); err != nil {
|
fmt.Sprintf(`{"level":"INFO","stacktracelevel":"NONE","colorize":%t,"flags":-1}`, colorize)); err != nil {
|
||||||
|
|
Loading…
Reference in New Issue