Feature #20433
closedConfig option to have crunch-run stop sending logs to logs table
100%
Related issues
Updated by Peter Amstutz about 1 month ago
- Target version changed from To be groomed to Development 2023-05-10 sprint
Updated by Peter Amstutz about 1 month ago
- Story points set to 0.5
- Assigned To set to Tom Clegg
- Category set to Crunch
Updated by Tom Clegg about 1 month ago
- Related to Story #16442: Scalable + reliable container logging added
Updated by Peter Amstutz about 1 month ago
- Assigned To changed from Tom Clegg to Brett Smith
Updated by Tom Clegg about 1 month ago
We already have this
# Maximum bytes that may be logged by a single job. Log bytes that are
# silenced by throttling are not counted against this total.
LimitLogBytesPerJob: 67108864
Perhaps we just need to ensure (and document) that setting this to 0 disables all the "create log" API calls (rather than meaning "unlimited").
Updated by Peter Amstutz 23 days ago
- Target version changed from Development 2023-05-10 sprint to Development 2023-05-24 sprint
Updated by Peter Amstutz 23 days ago
- Target version changed from Development 2023-05-24 sprint to Development 2023-06-07
Updated by Brett Smith 1 day ago
20433-crunch-log-zero-bytes-job @ f4cb9b474add3becb58dccaf555c2a52d15cbd27 - developer-run-tests: #3682
This branch does the bare minimum of testing the specific case where LimitLogBytesPerJob=0
and documenting the behavior. Note that in this case the container still creates a single log record noting that the throttle is in effect. I do think we should leave this as an affordance so users don't wonder why their Workbench log viewer is empty if they see that.
There are various things we could do to make this more user-friendly, but I assume none of them are worth time or effort given the plan to replace this system completely in the short-to-medium term.
Updated by Brett Smith about 8 hours ago
- Status changed from New to Resolved
Applied in changeset arvados|4e1e7f762ff1acd13b18efed5974b32833a467e2.