From df5350ac0dcd52a5c8d6d0d76da49461e30e6ba3 Mon Sep 17 00:00:00 2001 From: Peter Amstutz Date: Wed, 23 Aug 2023 14:58:43 -0400 Subject: [PATCH] 20894: Set LimitLogBytesPerJob to 0 Arvados-DCO-1.1-Signed-off-by: Peter Amstutz --- lib/config/config.default.yml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/lib/config/config.default.yml b/lib/config/config.default.yml index 18ffb1ca24..32727b1bce 100644 --- a/lib/config/config.default.yml +++ b/lib/config/config.default.yml @@ -1212,11 +1212,14 @@ Clusters: # before being silenced until the end of the period. LogThrottleLines: 1024 - # Maximum bytes that may be logged by a single job. Log bytes that are - # silenced by throttling are not counted against this total. - # If you set this to zero, each container will only create a single - # log on the API server, noting for users that logging is throttled. - LimitLogBytesPerJob: 67108864 + # Maximum bytes that may be logged as legacy log events + # (records posted to the "logs" table). Starting with Arvados + # 2.7, container live logging has migrated to a new system + # (polling the container request live log endpoint) and this + # value should be 0. As of this writing, the container will + # still create a single log on the API server, noting for that + # log events are throttled. + LimitLogBytesPerJob: 0 LogPartialLineThrottlePeriod: 5s -- 2.30.2