You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2019/06/24 22:08:00 UTC

[jira] [Commented] (MESOS-9124) Agent reconfiguration can cause master to unsuppress on scheduler's behalf

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

Benjamin Mahler commented on MESOS-9124:
----------------------------------------

Backporting this fix to active release branches.

> Agent reconfiguration can cause master to unsuppress on scheduler's behalf
> --------------------------------------------------------------------------
>
>                 Key: MESOS-9124
>                 URL: https://issues.apache.org/jira/browse/MESOS-9124
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation, master
>    Affects Versions: 1.5.3, 1.6.2, 1.7.2
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>            Priority: Major
>              Labels: foundations, mesosphere
>             Fix For: 1.8.0
>
>
> When agent reconfiguration was enabled in Mesos, the allocator was also updated to remove all offer filters associated with an agent when that agent's attributes change. In addition, whenever filters for an agent are removed, the framework is unsuppressed for any roles that had filters on the agent.
> While this ensures that schedulers will have an opportunity to use resources on an agent after reconfiguration, modifying the scheduler's suppression may put the scheduler in an inconsistent state, where it believes it is suppressed in a particular role when it is not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)