Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-703

master fails to respect updated FrameworkInfo when the framework scheduler restarts

    XMLWordPrintableJSON

    Details

    • Type: Epic
    • Status: Accepted
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.14.0
    • Fix Version/s: None
    • Component/s: master
    • Environment:

      ubuntu 13.04, mesos 0.14.0-rc3

    • Epic Name:
      update frameworkinfo
    • Sprint:
      Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1

      Description

      When I first ran marathon it was running as a personal user and registered with mesos-master as such due to putting an empty string in the user field. When I restarted marathon as "nobody", tasks were still being run as the personal user which didn't exist on the slaves. I know marathon was trying to send a FrameworkInfo with nobody listed as the user because I hard coded it in. The tasks wouldn't run as "nobody" until I restarted the mesos-master. Each time I restarted the marathon framework, it reregistered with mesos-master and mesos-master wrote to the logs that it detected a failover because the scheduler went away and then came back.

      I understand the scheduler failover, but shouldn't mesos-master respect an updated FrameworkInfo when the scheduler re-registers?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                curzonj Jordan Curzon
                Shepherd:
                Vinod Kone
              • Votes:
                2 Vote for this issue
                Watchers:
                22 Start watching this issue

                Dates

                • Created:
                  Updated: