You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "longfei (JIRA)" <ji...@apache.org> on 2019/01/11 10:18:00 UTC

[jira] [Commented] (MESOS-9394) Maintenance of machine A causes "Removing offers" for machine B.

    [ https://issues.apache.org/jira/browse/MESOS-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740255#comment-16740255 ] 

longfei commented on MESOS-9394:
--------------------------------

[~arojas] Hi, would you take a look at this pls.

I think 
{code:java}
if (master->machines[id].info.mode() != MachineInfo::UP) {
  master->machines[id].info.set_mode(MachineInfo::UP);
  master->updateUnavailability(id, None());
}
{code}
will fix this.

> 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
>            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)