Comment 7 for bug 1696970

@colin-king In this case the journal was not broken. Do you have many examples of really broken journals?

If so, do you have any solution in mind that would work better in scenarios you care about but don't cause regressions?

Proper infrastructure planning with (CPU) quotas in place where it matters seems to be a good practice instead of running highly loaded servers.

The 3 min default timer for systemd-journald seems appropriate or even generous.