-
Deprecated FieldsFieldDescriptionContinuous scheduling is known to cause locking issue inside Only used when
FairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDis enabledContinuous scheduling is known to cause locking issue inside Only used whenFairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDis enabledContinuous scheduling is known to cause locking issue inside Only used whenFairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDis enabledThe preferred way to configure the increment is by using the yarn.resource-types.{RESOURCE_NAME}.increment-allocation property, for memory: yarn.resource-types.memory-mb.increment-allocationThe preferred way to configure the increment is by using the yarn.resource-types.{RESOURCE_NAME}.increment-allocation property, for CPU: yarn.resource-types.vcores.increment-allocation
-
Deprecated MethodsMethodDescriptionlinked to
FairScheduler.isContinuousSchedulingEnabled()deprecationlinked toFairScheduler.isContinuousSchedulingEnabled()deprecationlinked toFairScheduler.isContinuousSchedulingEnabled()deprecationContinuous scheduling should not be turned ON. It is deprecated because it can cause scheduler slowness due to locking issues. Schedulers should use assignmultiple as a replacement.linked toFairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDdeprecationlinked toFairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDdeprecationlinked toFairSchedulerConfiguration.CONTINUOUS_SCHEDULING_ENABLEDdeprecationuseFairSchedulerConfiguration.ASSIGN_MULTIPLEto improve container allocation ramp up.Since it doesn't track cluster resource changes, replaced bySchedulingPolicy.initialize(FSContext).
FairSchedulerConfiguration.ASSIGN_MULTIPLEto improve container allocation ramp up.