Hi, I am trying to use the /maintenance API for mesos slave maintenance/drain.
I follow doc at http://mesos.apache.org/documentation/latest/maintenance/ I use mesos 1.0.1 on a single machine (for dev). When scheduling a node using { "windows" : [ { "machine_ids" : [ { "hostname" : "tifenn.irisa.fr", "ip" : "127.0.0.1" } ], "unavailability" : { "start" : { "nanoseconds" : 1472637340000000000 }, "duration" : { "nanoseconds" : 3600000000000 } } } ] } The start date is set in the recent past (setting to future did not change). I see in /maintenance/status {"draining_machines":[{"id":{"hostname":"tifenn.irisa.fr","ip":"127.0.0.1"}}]} However, the offers I receive do not contain the unavailibility parameter. I do not know if it is expected, but start/duration do not appear in maintenance/status result. I see in master logs: HTTP POST for /master/maintenance/schedule from 127.0.0.1:34858 with User-Agent='curl/7.43.0' I tried anyway to switch the node to maintenance (/maintenance/down) but I continue to receive offers for this slave. In status, I see my slave in machines_down: {"down_machines":[{"hostname":"tifenn.irisa.fr","ip":"127.0.0.1"}]} I can see on master logs: I0831 12:12:37.568898 6428 http.cpp:381] HTTP POST for /master/machine/down from 127.0.0.1:34970 with User-Agent='curl/7.43.0' .... Sending 1 offers to framework a559cd9e-3e58-4377-9e1a-c8f3d28d2318-0000 (Go-Docker Mesos) at [email protected]:43060 Should something be set to enable maintenance in mesos ? Thanks Olivier
