Arvados

#20200 added a limit where the controller will return 503 to log create requests if they start taking up too much of the request capacity (configured by Services.API.LogCreateRequestFraction). If this happens, then the container's log collection provides the most up-to-date logs a user can view. Crunch updates this collection periodically (configured by Containers.Logging.LogUpdatePeriod). However, if the controller never drops a log update, then the live logs have the most up-to-date logs.

Currently the user has no way to know whether live logs have been dropped. Therefore, if they want the most recent logs from a container, their only option is to check both places.

One way or another, client tools like Workbench should figure out which source has the most recent logs, and render logs from there.

This ticket may be obsoleted, and not done, if we make sufficient progress on live logs revamp #16442.