[
https://issues.apache.org/jira/browse/MESOS-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740647#comment-16740647
]
Benno Evers commented on MESOS-9394:
------------------------------------
Both the analysis and the proposed change look correct to me - the current
behaviour certainly does not match what the documentation at
http://mesos.apache.org/documentation/latest/maintenance/#scheduling-maintenance
suggests.
[~carlone], if you want to keep credit for the fix I'd suggest to go ahead and
post a patch to reviewboard, otherwise if you prefer I can also go ahead and do
that for you.
> Maintenance of machine A causes "Removing offers" for machine B.
> ----------------------------------------------------------------
>
> Key: MESOS-9394
> URL: https://issues.apache.org/jira/browse/MESOS-9394
> Project: Mesos
> Issue Type: Bug
> Reporter: longfei
> Assignee: longfei
> Priority: Major
> Labels: maintenance
>
> If I schedule machine A in a maintenance call, the logic in
> "___updateMaintenanceSchedule" will check all the master's machines.
> Another machine(say machine B) not in the maintenance schedule will be set to
> UP Mode and call "updateUnavailability". This results in removing all offers
> of slaves on machine B.
> If I am using these offers to run some tasks, these tasks would be lost for
> REASON_INVALID_OFFERS.
> I think a maintenance schedule should not affect machines not in it. Is that
> right?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
