[ https://issues.apache.org/jira/browse/MESOS-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848973#comment-15848973 ]
Anindya Sinha commented on MESOS-7015: -------------------------------------- To answer your questions: (1) Yes, that is indeed the use case. If there are a large number of frameworks with most of them suppressed, then on a master failover all of these frameworks become unsuppressed currently which increases load on master. The frameworks need to {{SUPPRESS}} the offers to get back to suppressed mode. Instead, we can achieve that in a single {{SUBSCRIBE}} instead. (2) If we add a {{optional bool suppressed}} in {{FrameworkInfo}} where {{suppressed}} defaults to {{false}}, then we can do this for both v0 and v1, and would not need change in {{Call::SUBSCRIBE}} as well (since {{FrameworkInfo}} is a part of {{SUBSCRIBE}} for both v0 and v1). However, we need to make sure we update this boolean flag on master on {{SUPPRESS}} and {{REVIVE}} calls as well (like we do in the allocator). Otherwise, we would need to change the scheduler driver API to add this {{suppressed}} flag instead to make it work for v0. I agree it should be trivial in v1 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)