Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Won't Do
    • Affects Version/s: Marathon 1.5.5
    • Fix Version/s: None
    • Labels:

      Description

      When a task becomes unhealthy and exceeds maxConsecutiveFailure, Marathon starts to kill the task the same way as when upgrading/restarting application:

       

      SIGTERM -> taskKillGracePeriodSeconds -> SIGKILL
      

      However there's no reason to let unhealthy task finish his job. Killing it asap with SIGKILL should be done instead.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              bydga bydga
              Team:
              ( DO NOT USE ) Orchestration Team
              Watchers:
              bydga, Tim Harper
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: