Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently the sorter relies on the caller to make sure the sorter is in a good state when add/activate is called. It's not defensive against caller mistakes as it should be. It's never an acceptable result if duplicates are added to DRFSorter::clients.
Attachments
Issue Links
- is related to
-
MESOS-4694 DRFAllocator takes very long to allocate resources with a large number of frameworks
- Resolved
- relates to
-
MESOS-5280 Inconsistent error checking in DRF sorter.
- Open