Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.1
-
None
-
Incompatible change, Reviewed
-
Description
The Fair Scheduler never cleans up queues even if they are deleted in the allocation file, or were dynamically created and are never going to be used again. Queues always remain in memory which leads to two following issues.
- Steady fairshares aren’t calculated correctly due to remaining queues
- WebUI shows deleted queues, which is confusing for users (
YARN-4022).
We want to support proper queue deletion without restarting the Resource Manager:
- Static queues without any entries that are removed from fair-scheduler.xml should be deleted from memory.
- Dynamic queues without any entries should be deleted.
- RM Web UI should only show the queues defined in the scheduler at that point in time.
Attachments
Attachments
Issue Links
- causes
-
YARN-8990 Fix fair scheduler race condition in app submit and queue cleanup
- Resolved
-
YARN-8420 Multithreaded correctness Warning occurs in AllocationFileLoaderService
- Resolved
-
YARN-8390 Fix API incompatible changes in FairScheduler's AllocationFileLoaderService
- Resolved
-
YARN-8994 Fix race condition between move app and queue cleanup in Fair Scheduler
- Resolved
- incorporates
-
YARN-5399 Add configuration to remember ad-hoc queues upon configuration reload
- Resolved
- is blocked by
-
YARN-8268 Fair scheduler: reservable queue is configured both as parent and leaf queue
- Resolved
- is duplicated by
-
YARN-4022 queue not remove from webpage(/cluster/scheduler) when delete queue in xxx-scheduler.xml
- Resolved