Story #8552

[Crunch] Log throttling shouldn't throttle logs from crunchstat, crunch-job

Added by Peter Amstutz almost 6 years ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

While reviewing #7399 it occurred to me that we could be even smarter and only apply throttling to non-crunchstat stderr lines, which represents useful logging that's coming from the infrastructure.

Related issues

Related to Arvados - Feature #7399: [Crunch] [UX] Improve log throttlingResolved09/29/2015

History

#1 Updated by Peter Amstutz almost 6 years ago

  • Description updated (diff)

#2 Updated by Brett Smith almost 6 years ago

  • Tracker changed from Support to Story

#3 Updated by Brett Smith almost 6 years ago

  • Target version set to Arvados Future Sprints

#4 Updated by Tom Morris about 5 years ago

The story for #7399 actually explicitly mentions that opposite as a user suggested potential fix - filter crunchstat lines so that the more important (to that user) non-system infrastructure lines get priority.

#5 Updated by Ward Vandewege 6 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF