> I know DRAIN_AGENT is only for mesos 1.9. But what use it to post a
> maintenance schedule, see the node being marked as draining, and nothing
> happens with the tasks?

The maintenance schedules require that schedulers implement support for
them. Nothing happens if the scheduler does not have support for the
maintenance schedules.
The DRAIN_AGENT in Mesos 1.9 does not require scheduler support (Mesos will
kill the tasks). As a result, it is up to the operator issuing the
DRAIN_AGENT request to not violate higher level SLAs.
See this thread for context:
https://lists.apache.org/thread.html/c0414897debdea2faffbffc81fa36c435e109e7ff80c72c544b4d135@%3Cdev.mesos.apache.org%3E

As to what support marathon has for maintenance schedules, the ticket you
pointed to what closed in favor of
https://jira.mesosphere.com/browse/DCOS-54915.
This new ticket is only about DRAIN_AGENT as far as I can tell. If so, then
there is a gap in the marathon ticketing for supporting SLA aware
maintenance.

On Thu, Aug 8, 2019 at 4:22 PM Marc Roos <[email protected]> wrote:

>
> I don’t get from this page
> http://mesos.apache.org/documentation/latest/maintenance/ if mesos
> should be 'moving' tasks to another node when it is marked as draining.
> I know DRAIN_AGENT is only for mesos 1.9. But what use it to post a
> maintenance schedule, see the node being marked as draining, and nothing
> happens with the tasks?
>
>
> On the marathon page the say "draining is not yet implemented", yet they
> refer to an issue that has been resolved.
> https://mesosphere.github.io/marathon/docs/maintenance-mode.html
>
>
> On stackoverflow there is the same question, and again referencing issue
> that have been resolved.
>
> https://stackoverflow.com/questions/37194123/marathon-tasks-not-migrating-off-mesos-node-goes-into-draining-mode
> https://jira.mesosphere.com/browse/MARATHON-3216
> https://phabricator.mesosphere.com/D1069
>
>
>
> -----Original Message-----
> From: Vinod Kone [mailto:[email protected]]
> Sent: donderdag 8 augustus 2019 0:35
> To: user
> Subject: Re: Draining: Failed to validate master::Call: Expecting 'type'
> to be present
>
> Please read the "maintenace primitives" section in this doc
> http://mesos.apache.org/documentation/latest/maintenance/ and let us
> know if you have unanswered questions.
>
> On Wed, Aug 7, 2019 at 4:59 PM Marc Roos <[email protected]>
> wrote:
>
>
>
>          I seem to be able to add a maintenance schedule, and get also a
> report
>         on '{"down_machines":[{"hostname":"m02.local"}]}' but I do not see
> tasks
>         migrate to other hosts. Or is this not the purpose of maintenance
> mode
>         in 1.8? Just to make sure no new tasks will be launched on hosts
>         scheduled for maintenance?
>
>
>
>         -----Original Message-----
>         From: Chun-Hung Hsiao [mailto:[email protected]]
>         Sent: woensdag 7 augustus 2019 22:59
>         To: user
>         Subject: Re: Draining: Failed to validate master::Call: Expecting
> 'type'
>         to be present
>
>         Hi Marc.
>
>         Agent draining is a Mesos 1.9 feature and is only available on the
>         current Mesos master branch.
>         Please see https://issues.apache.org/jira/browse/MESOS-9814.
>
>         Best,
>         Chun-Hung
>
>         On Wed, Aug 7, 2019 at 1:35 PM Marc Roos <[email protected]>
>
>
>         wrote:
>
>
>
>                 Should this be working in mesos 1.8?
>
>                 [@m01 ~]# curl --user test:xxxxxxxxx -X POST \
>                 >   https://m01.local:5050/api/v1 \
>                 >   --cacert /etc/pki/ca-trust/source/ca.crt \
>                 >   -H 'Accept: application/json' \
>                 >   -H 'content-type: application/json' -d '{
>                 >   "type": "DRAIN_AGENT",
>                 >   "drain_agent": {"agent_id": {
>                 >     "value":"53336fcb-7756-4673-b9c7-177e04f34c3b-S1"
>                 >   }}}'
>
>                 Failed to validate master::Call: Expecting 'type' to be
> present
>
>
>
>
>
>
>
>

Reply via email to