[jira] [Updated] (MESOS-7460) UpdateFrameworkMessage may send a Framework role(s) change to a non-MULTI_ROLE agent.

["Adam B (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam B updated MESOS-7460:
--------------------------
    Target Version/s:   (was: 1.2.1, 1.3.0)

> UpdateFrameworkMessage may send a Framework role(s) change to a non-MULTI_ROLE agent.
> -------------------------------------------------------------------------------------
>
>                 Key: MESOS-7460
>                 URL: https://issues.apache.org/jira/browse/MESOS-7460
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.3.0
>            Reporter: Benjamin Mahler
>            Assignee: Michael Park
>            Priority: Blocker
>
> When a framework is MULTI_ROLE capable, if the framework was previously running tasks on an old agent (non-MULTI_ROLE capable), the master *must* ensure the UpdateFramework message sent to this old agent preserves the framework's original role. Otherwise the agent will interpret the role to have changed, which can break things (e.g. not locate the reservations, volumes, etc).
> In addition, a framework without MULTI_ROLE has the ability to change their role. We'll need to change this to ensure that the {{role}} field is immutable and frameworks need to use the {{roles}} field with the MULTI_ROLE capability if they want to change their role.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)