Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Try to improve the case, Spark Dynamic Allocation when we enable gang scheduling:
If we can add some improvements to this case? Such as:
For preemption case:
lower priority for anything more than the gang and thus get them killed earlier than when they do not belong to a gang
For quota hit:
For normal gang scheduling, we will reject jobs with total gang size > quota, but for dynamic allocations, if we can add monitor logic to monitor the exceeded resource allocations for those jobs?
- We may extend the quota some value when it happens?