[MESOS-3038] Resource offers do not contain Unavailability, given a maintenance schedule - ASF JIRA

XML

Word

Printable

JSON

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.

is blocked by

MESOS-2066 Add optional 'Unavailability' to resource offers to provide maintenance awareness.

MESOS-2067 Add HTTP API to the master for maintenance operations.

MESOS-3045 Maintenance information is not populated in case of failover

Is contained by

MESOS-2076 Implement maintenance primitives in the Master.