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

Resource offers do not contain Unavailability, given a maintenance schedule

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.25.0
    • Component/s: allocation, master
    • Labels:
    • Target Version/s:
    • Epic Link:
    • Sprint:
      Mesosphere Sprint 17, Mesosphere Sprint 18
    • Story Points:
      8

      Description

      Given a schedule, defined elsewhere, any resource offers to affected slaves must include an Unavailability field.

      The maintenance schedule for a single slave should be held in persistent storage and locally by the master. i.e. In src/master/master.hpp:

      struct Slave {
        ... // Existing fields.
      
        // New field that the master/allocator can access
        Maintenances pendingDowntime;
      }
      

      The new field should be populated via an API call (see MESOS-2067).

      The Unavailability field can be added to Master::offer (src/master/master.cpp).

      offer->mutable_unavailability()->MergeFrom(slave->pendingDowntime);
      

      Possible test(s):

      • PendingUnavailibilityTest
        • Start master, slave.
        • Check unavailability of offer == none.
        • Set unavailability to the future.
        • Check offer has unavailability.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jvanremoortere Joris Van Remoortere
                Reporter:
                kaysoky Joseph Wu
                Shepherd:
                Benjamin Hindman
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: