[
https://issues.apache.org/jira/browse/MESOS-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017787#comment-16017787
]
Anindya Sinha commented on MESOS-7015:
--------------------------------------
Based on additional discussion, following is the approach decided to address
this:
1. Add {{repeated string suppressed_roles}} to {{Call::Subscribe} which
represents a subset of roles which are suppressed. Offers pertaining to the
suppressed roles shall not be sent out.
2. {{SUPPRESS}} and {{REVIVE}} calls will toggle the (de)activation mode of the
roles.
3. Allocator's {{activateFramework()}} call will activate all roles of the
framework which are not in {{suppressed_roles}}. Similarly, in
{{deactivateFramework()}} call will deactivate all roles that are not
suppressed already.\
Note that this functionality shall not be added fir scheduler driver. I opened
https://issues.apache.org/jira/browse/MESOS-7526 to address that.
> Frameworks should be able to (re)register in suppressed state
> -------------------------------------------------------------
>
> Key: MESOS-7015
> URL: https://issues.apache.org/jira/browse/MESOS-7015
> Project: Mesos
> Issue Type: Improvement
> Components: allocation, framework
> Reporter: Anindya Sinha
> Assignee: Anindya Sinha
>
> We should consider allowing frameworks to specify their "suppressed mode"
> when they register or re-register with the mesos master.
> This should help to keep traffic and the load on the cluster low especially
> when there are high number of frameworks and/or agents in the cluster during
> failovers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
