[
https://issues.apache.org/jira/browse/MESOS-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone resolved MESOS-249.
------------------------------
Resolution: Not a Problem
Looks like this was intentional.
>From allocator's deactivateFramework() code:
{code}
// Note that the Sorter *does not* remove the resources allocated
// to this framework. For now, this is important because if the
// framework fails over and is activated, we still want a record
// of the resources that it is using. We might be able to collapse
// the added/removed and activated/deactivated in the future.
// Do not delete the filters contained in this
// framework's 'filters' hashset yet, see comments in
// HierarchicalAllocatorProcess::reviveOffers and
// HierarchicalAllocatorProcess::expire.
frameworks[frameworkId].filters.clear();
{code}
> DRF allocator does't expire filters correctly
> ---------------------------------------------
>
> Key: MESOS-249
> URL: https://issues.apache.org/jira/browse/MESOS-249
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Labels: twitter
>
> When a framework gets deactivated before its filters have expired, the
> filters are never removed from the DRF allocator. This will result in the
> failed over framework never getting resource offers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
