Arvados

edit: we already have a configuration knob for this. It has "none", "errors" and "all" and defaults to "none" with the reasoning being that logging errors can show configuration information to users that the admin might prefer not to reveal.

original text:

I'm looking at a container that ran for 4 hours and ran a very data-intensive task. The keepstore.txt is 160 MiB which is 100x as large as the next largest file in the log collection (130 KiB). Since logs tend to hang around for a while, this is an unfortunate use of space.

The most straightforward solution is probably to turn the logging level down to "warnings and errors".