[
https://issues.apache.org/jira/browse/MESOS-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074875#comment-16074875
]
Tomasz Janiszewski commented on MESOS-5675:
-------------------------------------------
https://lists.apache.org/thread.html/22ec645c835552e7c6b03ffb61368f814765c8a701d4736efa4eb205@%3Cuser.mesos.apache.org%3E
> 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.4.14#64029)
