Commit 999e703
committed
resolver: less debug
Observed lots of debug messages from resolver (and associated high CPU
usage because of lots of logging) when debug logging is turned on. Here
is some data from a real system:
> $ journalctl -u docker --since="2019-10-21 21:00:00" --until="2019-10-21 22:00:00" | wc -l
> 188621
> $ journalctl -u docker --since="2019-10-21 21:00:00" --until="2019-10-21 22:00:00" | grep -E 'Name To resolve: |\[resolver\] ' | wc -l
> 186319
So, it was about 200000 lines logger for just one hour, and about 99%
of that are from resolver. While this might be the peculiarity of
a particular setup, the number of such messages still seem way too
excessive.
Remove the ones that are not errors.
Signed-off-by: Kir Kolyshkin <[email protected]>1 parent 79c19d0 commit 999e703
2 files changed
+0
-12
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
255 | 255 | | |
256 | 256 | | |
257 | 257 | | |
258 | | - | |
259 | | - | |
260 | 258 | | |
261 | 259 | | |
262 | 260 | | |
| |||
296 | 294 | | |
297 | 295 | | |
298 | 296 | | |
299 | | - | |
300 | 297 | | |
301 | 298 | | |
302 | 299 | | |
| |||
452 | 449 | | |
453 | 450 | | |
454 | 451 | | |
455 | | - | |
456 | | - | |
457 | | - | |
458 | 452 | | |
459 | 453 | | |
460 | 454 | | |
| |||
522 | 516 | | |
523 | 517 | | |
524 | 518 | | |
525 | | - | |
526 | 519 | | |
527 | 520 | | |
528 | 521 | | |
529 | 522 | | |
530 | | - | |
531 | 523 | | |
532 | 524 | | |
533 | 525 | | |
534 | | - | |
535 | | - | |
536 | | - | |
537 | 526 | | |
538 | 527 | | |
539 | 528 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
529 | 529 | | |
530 | 530 | | |
531 | 531 | | |
532 | | - | |
533 | 532 | | |
534 | 533 | | |
535 | 534 | | |
| |||
0 commit comments