[
https://issues.apache.org/jira/browse/MESOS-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangya Liu reassigned MESOS-6854:
----------------------------------
Assignee: Guangya Liu
> Prevent launching MULTI_ROLE framework's tasks on agents without MULTI_ROLE
> support.
> ------------------------------------------------------------------------------------
>
> Key: MESOS-6854
> URL: https://issues.apache.org/jira/browse/MESOS-6854
> Project: Mesos
> Issue Type: Task
> Components: agent, master
> Reporter: Benjamin Mahler
> Assignee: Guangya Liu
>
> The proposal for upgrades / backwards compatibility in phase 1 of multi-role
> framework support is that we require that masters and agents are all upgraded
> before a multi-role framework registers.
> We need to explicitly protect against this situation occurring given it's
> common for old agents to show up in a cluster. The master can prevent the
> launching of MULTI_ROLE frameworks' tasks on agent without MULTI_ROLE
> framework support.
> If we were to naively let this happen the old agent would think the resources
> are allocated to the "*" and there would need to be master logic to deal with
> the old agent not populating Resource.AllocationInfo.
> The guard will either need to be version based or agent capability based, the
> latter seeming like the stronger approach given some users upgrade off of
> master rather than using release versions.
> We can initially start with the master side guard, and have the agent send
> the capability once the agent-side implementation is complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
