[
https://issues.apache.org/jira/browse/MESOS-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946205#comment-14946205
]
Guangya Liu commented on MESOS-3587:
------------------------------------
[~bmahler] Can you please show more detail for why (1) is required? Why the
filter needs to be cleared? In my understanding, the filter should be kept to
aggregate more resources for resource offers, comments? Thanks.
> Framework failover when framework is 'active' does not trigger allocation.
> --------------------------------------------------------------------------
>
> Key: MESOS-3587
> URL: https://issues.apache.org/jira/browse/MESOS-3587
> Project: Mesos
> Issue Type: Bug
> Components: allocation, master
> Reporter: Benjamin Mahler
> Assignee: Marco Massenzio
> Priority: Minor
> Labels: mesosphere
>
> FWICT, this is just a consequence of some technical debt in the master code.
> When an active framework fails over, we do not go through the
> deactivation->activation code paths, and so:
> (1) The framework's filters in the allocator remain after the failover.
> (2) The failed over framework does not receive an immediate allocation (it
> has to wait for the next allocation interval).
> If the framework had disconnected first, then the failover goes through the
> deactivation->activation code paths.
> This also means that some tests take longer to run than necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
