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 2017/01/10 18:49:58 UTC

[jira] [Commented] (MESOS-5675) Add support for master capabilities

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

Benjamin Mahler commented on MESOS-5675:
----------------------------------------

Is there a ticket for agent capabilities as well? E.g. the master was upgraded to support feature X but only some of the agents were upgraded.

> Add support for master capabilities
> -----------------------------------
>
>                 Key: MESOS-5675
>                 URL: https://issues.apache.org/jira/browse/MESOS-5675
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Neil Conway
>              Labels: mesosphere
>
> Right now, frameworks can advertise their capabilities to the master via the {{FrameworkInfo}} they use for registration/re-registration. This allows masters to provide backward compatibility for old frameworks that don't support new functionality.
> To allow new frameworks to support backward compatibility with old masters, the inverse concept would be useful: masters would tell frameworks which capabilities are supported by the master, which the frameworks could then use to decide whether to use features only supported by more recent versions of the master.
> For now, frameworks can workaround this by looking at the master's version number, but that seems a bit fragile and hacky.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)