-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.0.0
-
Fix Version/s: None
-
Component/s: fairscheduler
-
Labels:None
Method Fairscheduler#shouldAttemptPreemption doesn't consider resources other than vcore and memory. We may need to rethink it in the resource type scenario. cc Miklos Szegedi, Wilfred Spiegelenburg and Szilard Nemeth.
if (context.isPreemptionEnabled()) { return (context.getPreemptionUtilizationThreshold() < Math.max( (float) rootMetrics.getAllocatedMB() / getClusterResource().getMemorySize(), (float) rootMetrics.getAllocatedVirtualCores() / getClusterResource().getVirtualCores())); }
- depends upon
-
YARN-9019 Ratio calculation of ResourceCalculator implementations could return NaN
-
- Resolved
-
-
YARN-9025 TestFairScheduler#testChildMaxResources is flaky
-
- Resolved
-
-
YARN-8842 Expose metrics for custom resource types in QueueMetrics
-
- Resolved
-
-
YARN-8750 Refactor TestQueueMetrics
-
- Resolved
-
- is blocked by
-
YARN-9047 FairScheduler: default resource calculator is not resource type aware
-
- Open
-
- is depended upon by
-
YARN-5106 Provide a builder interface for FairScheduler allocations for use in tests
-
- Resolved
-
- relates to
-
YARN-8842 Expose metrics for custom resource types in QueueMetrics
-
- Resolved
-