Bug #5534

[Workbench] Log tab takes too long to load with large logs

Added by Peter Amstutz over 5 years ago. Updated over 5 years ago.

Assigned To:
Radhika Chippada
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)
Story points:


With a very long running pipeline, like tb05z-d1hrv-lx5w1pngtl2poj9, when you click on the "Log" tab, it spins for a while and then fails with "504 Gateway Time-out". Presumably workbench is loading too much logs and it is taking too long.


Task #5551: Review branch: 5534-limit-log-linesResolvedRadhika Chippada

Associated revisions

Revision 8ddb4573
Added by Radhika Chippada over 5 years ago

closes #5534
Merge branch '5534-limit-log-lines'


#1 Updated by Peter Amstutz over 5 years ago

  • Description updated (diff)

#2 Updated by Radhika Chippada over 5 years ago

  • Category set to Workbench
  • Status changed from New to In Progress
  • Assigned To set to Radhika Chippada
  • Target version changed from Bug Triage to 2015-04-01 sprint

This pipeline instance is still running as of this writing, so far running for 1 day and 14 hours and 5+ minutes. So far it has 100327+ log lines.

Workbench is trying to retrieve all of those lines and eventually timing out.

I now am limiting the number of log lines fetched to 2000. Now I see the log, with the newest 2000 log lines. And since the pipeline is still running, I am seeing log roll with newer lines from event log.

I was also able to see the log successfully using a limit size of 10000; however, in this case, fetching those many log lines took more than a minute. I hence feel that it is better to get less number of rows than make the user wait longer.

#3 Updated by Peter Amstutz over 5 years ago


#4 Updated by Radhika Chippada over 5 years ago

  • Status changed from In Progress to Resolved

Applied in changeset arvados|commit:8ddb457318d535fadad9a5554e2944cec96b17df.

Also available in: Atom PDF