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

          blocks

          Task - A task that needs to be done. AURORA-687 Aurora should set FrameworkInfo.principal

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Task - A task that needs to be done. MESOS-1719 Master should persist framework information

          • Major - Major loss of function.
          • Accepted
          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-751 Move to online updates of cached FrameworkInfo

          • Major - Major loss of function.
          • Resolved

          Wish - General wishlist item. MESOS-2006 update FrameworkInfo when a framework reregistered

          • Major - Major loss of function.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MESOS-2570 webuiUrl doesn't get updated when a framework re-registers

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-1218 Support changing framework failover timeouts

          • Major - Major loss of function.
          • Resolved
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-6627 Allow frameworks to modify the role(s) they are subscribed to.

          • Major - Major loss of function.
          • Resolved

          Wish - General wishlist item. MESOS-1828 The Mesos UI should link to framework UIs

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MESOS-2842 Master crashes when framework changes principal on re-registration

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-9747 Make behaviour of re-subscription consistent with UPDATE_FRAMEWORK.

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-2841 FrameworkInfo should include a Labels field to support arbitrary, lightweight metadata

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-7258 Provide scheduler calls to subscribe to additional roles and unsubscribe from roles.

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-8582 Pass FrameworkInfo to agents when applying operations

          • Major - Major loss of function.
          • Accepted

            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: