You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jay Guo (JIRA)" <ji...@apache.org> on 2017/01/20 06:30:27 UTC
[jira] [Assigned] (MESOS-6940) Do not send offers to MULTI_ROLE
schedulers if agent does not have MULTI_ROLE capability.
[ https://issues.apache.org/jira/browse/MESOS-6940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Guo reassigned MESOS-6940:
------------------------------
Assignee: Jay Guo
> Do not send offers to MULTI_ROLE schedulers if agent does not have MULTI_ROLE capability.
> -----------------------------------------------------------------------------------------
>
> Key: MESOS-6940
> URL: https://issues.apache.org/jira/browse/MESOS-6940
> Project: Mesos
> Issue Type: Task
> Components: allocation, master
> Reporter: Benjamin Mahler
> Assignee: Jay Guo
>
> Old agents that do not have the MULTI_ROLE capability cannot correctly receive tasks from schedulers that have the MULTI_ROLE capability *and are using multiple roles*. In this case, we should not send the offer to the scheduler, rather than sending an offer but rejecting the scheduler's operations.
> Note also that since we allow a single role scheduler to upgrade into having the MULTI_ROLE capability (use of the {{FrameworkInfo.roles}} field) so long as they continue to use a single role (in phase 1 of multi-role support the roles cannot be changed), we could continue sending offers if the scheduler is MULTI_ROLE capable but only uses a single role.
> In phase 2 of multi-role support, we cannot safely allow a MULTI_ROLE scheduler to receive resources from a non-MULTI_ROLE agent, so it seems we should simply disallow MULTI_ROLE schedulers from receiving offers from non-MULTI_ROLE agents, regardless of how many roles the scheduler is using.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)