Loading...

XML

Word

Printable

Type: Task
Resolution: Done-Errata
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Component/s: quay
Labels:
- triaged

Blocked:
False
Blocked Reason:
None
Ready:
False
Estimated Difficulty:
Low
Product:
Quay Enterprise
Intelligence Requested:
Market:

Customer Impact:

Customer Facing, Customer Reported

Target Version:

quay-v3.12.3

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Even after removing the DEBUG variable there are about 2500 lines per minute per pod. The log messages are all from type [INFO]. Most messages are like below ( Approximately 2000 lines per minute)

   "2023-11-27 15:24:05,825 [80] [INFO] [util.migrate.allocator] No candidates, marking entire block completed 210690-213109
    2023-11-27 15:24:05,832 [80] [INFO] [util.migrate.allocator] No candidates, marking 
    2023-11-27 15:24:05,868 [80] [INFO] [util.migrate.allocator] No candidates, marking entire block completed 136710-139129
    .
    .
    .
    2023-11-27 15:24:05,897 [80] [INFO] [util.migrate.allocator] No candidates, marking entire block completed 229355-231774"}}

The log message from above is missing the worker that is printing them.
For large registries it is getting a bit noisy. can we hide it as a debug message rather than info?