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

Guangya Liu commented on MESOS-6854:
------------------------------------




I am out of the office until 01/24/2017.

I will be in vacation from 1.16 to 1.24 and may not check email on time,
plesae call 15029181175 (Temp use) or wechat for any emergency. Thanks.



Note: This is an automated response to your message "[jira] [Assigned]
(MESOS-6854) Prevent launching MULTI_ROLE framework's tasks on agents
without MULTI_ROLE support." sent on 01/16/2017 07:42 AM GMT

This is the only notification you will receive while this person is away.


> 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: Jay Guo
>
> 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)

Reply via email to