Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65835

Certain tasks have timeouts set higher than default

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc6, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0
    • DAG 2022-05-02
    • 180
    • 2

      Motivation for Request

      Reduce log size and overall build resources by timing out tasks faster.

      Context

      Certain builds might take a long time to be considered hanging in case an unexpected failure happens increasing the use of resources and the generated logs.

      Description

      While revisiting how MongoDB networking layer connects to other processes, multiple builds stalled due unexpected errors and crashes. SERVER-63872 tighter idle timeouts to under 30 minutes but certain tasks have their timeout overwritten to a higher duration[1]. Longer tasks are expected to generate larger logs which are cumbersome to work with and generally can't be loaded by the internal tool Lobster.

      [1]:

      [2022/03/16 20:37:40.507] [2022-03-16 20:37:40,507 - __main__ - INFO] 2022-03-16 20:37.40 Overriding required-builder timeout exec_timeout_secs=4800.0
      [2022/03/16 20:37:40.756] [2022-03-16 20:37:40,756 - __main__ - INFO] 2022-03-16 20:37.40 Using historic based timeout   exec_timeout_secs=10860
      

            Assignee:
            david.bradford@mongodb.com David Bradford (Inactive)
            Reporter:
            daniel.morilha@mongodb.com Daniel Morilha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: