Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.8.2
-
None
-
None
-
Reviewed
Description
Only a problem in 2.8.
Preemption could oscillate due to the difference in how user limit is calculated between 2.8 and later releases.
Basically (ignoring ULF, MULP, and maybe others), the calculation for user limit on the Capacity Scheduler side in 2.8 is total used resources / number of active users while the calculation in later releases is total active resources / number of active users. When intra-queue preemption was backported to 2.8, it's calculations for user limit were more aligned with the latter algorithm, which is in 2.9 and later releases.
Attachments
Attachments
Issue Links
- is related to
-
YARN-7469 Capacity Scheduler Intra-queue preemption: User can starve if newest app is exactly at user limit
- Resolved