[arvados] updated: 2.6.0-533-gdf5350ac0d

[git repository hosting]

Summary of changes:
 lib/config/config.default.yml | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

       via  df5350ac0dcd52a5c8d6d0d76da49461e30e6ba3 (commit)
      from  0787f110e5ed61b358901fe38796e7ef0008deac (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit df5350ac0dcd52a5c8d6d0d76da49461e30e6ba3
Author: Peter Amstutz <peter.amstutz at curii.com>
Date:   Wed Aug 23 14:58:43 2023 -0400

    20894: Set LimitLogBytesPerJob to 0
    
    Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz at curii.com>

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
 

-----------------------------------------------------------------------


hooks/post-receive
--