Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-3603

task_launch_timeout vs task_launch_confirm timeout in docs

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Marathon 1.6.322, DC/OS 1.10.6
    • Component/s: Docs
    • Labels:
      None

      Description

      These should probably reference each other. I was using task_launch_timeout and was caught off-guard when things were still getting killed at 5 minutes.

      Maybe consider setting task_launch_timeout default to 6 minutes as well since it doesn't make sense for them to have the same value, especially when they're checked a few lines from one another in the code.

        Attachments

          Activity

            People

            • Assignee:
              matthias.eichstedt Matthias Eichstedt
              Reporter:
              GitHub_abraithwaite Alan Braithwaite (Inactive)
              Team:
              Orchestration Team
              Watchers:
              Jason Gilanfarr (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: