[
https://issues.apache.org/jira/browse/MESOS-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848821#comment-15848821
]
Vinod Kone commented on MESOS-7015:
-----------------------------------
Just so that I understand the motivation, are you trying to optimize for the
case where a bunch of frameworks have currently revived offers, but immediately
after a master failover all the re-registering frameworks are automatically
un-suppressed and need to be suppressed by frameworks again?
For the solution you proposed, how are you envisioning frameworks to
re-register in suppressed state? AFAICT, it's not easy to do so in the old
driver based world because it needs backwards incompatible API changes or
environment variable based hacks. It would be fairly easy to do in v1 API
though.
> 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
>
> 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)
