[MESOS-9616] `Filters.refuse_seconds` declines resources not in offers.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.4, 1.6.3, 1.7.3, 1.8.1, 1.9.0
• Component/s: allocation
• Labels: mesosphere mesosphere-dss-ga resource-management storage
• Target Version/s: 1.7.3, 1.8.1, 1.9.0
• Sprint: Storage R11 Sprint 40, Storage: RI-12 Sprint 43, Storage: RI-13 Sprint 44, Storage: RI-13 Sprint 45
• Story Points: 2
• Assignee: Chun-Hung Hsiao
• Reporter: Chun-Hung Hsiao
• Shepherd: Benjamin Mahler
• Created: 27/Feb/19 23:12
• Updated: 01/May/19 21:19
• Resolved: 01/May/19 21:19

Description

The documentation of Filters.refuse_seconds says:

Also, any of the offer’s resources not used in the ACCEPT call (e.g., to launch a task or task group) are considered declined and might be reoffered to other frameworks, meaning that they will not be reoffered to the scheduler for the amount of time defined by the filter.

Consider an ACCEPT call with just a CREATE operation, but no LAUNCH or LAUNCH_GROUP. The CREATE call will generate a persistent volume resource that is not in the offer's resources, but it will still not be reoffered to the scheduler for the amount of time defined by the filter.

Also, the term used is vague here. If we have an ACCEPT call with a CREATE on a disk followed by a DESTROY on the created persistent volume, would the disk be considered used?

Issue Links

• blocks: MESOS-5804 ExamplesTest.DynamicReservationFramework is flaky