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

Failed write to group:root upon application launch

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Marathon 1.4.0
    • Component/s: None
    • Labels:
      None

      Description

      Marathon 1.1.1
      Mesos 0.28.0

      I found an interesting issue that I'm looking to gather feedback on. On Marathon 1.1.1 it seems that a proper write was made to an application's ZK path and the application was launched by Marathon.

      We found that that same update did not happen to the general group:root node that seemingly stores all of the information for the global set of applications. So when we made a request to the the /apps API to check if the application was launched, it said no and it could not be searched for in the UI. But we could visit the exact path in the UI to find the running applications and seemingly hit the API at that applications exact path.

      Can anyone think of a reason that the group:root node would not be updated or would be unsuccessful?

      We "fixed" this by making a minor change to the 6 affected applications to trigger a new deployment of them in Marathon.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              GitHub_cmluciano cmluciano (Inactive)
              Team:
              Orchestration Team
              Watchers:
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: