|Modifier and Type||Field and Description|
**DO NOT USE** Whether
|Constructor and Description|
public static final ConfigOption<Boolean> MATCH_CONTAINER_VCORES
YarnResourceManagershould match the vcores of allocated containers with those requested.
By default, Yarn ignores vcores in the container requests, and always allocate 1 vcore for each container. Iff 'yarn.scheduler.capacity.resource-calculator' is set to 'DominantResourceCalculator' for Yarn, will it allocate container vcores as requested.
For Hadoop 2.6+, we can learn whether Yarn matches vcores from
RegisterApplicationMasterResponse. However, this is not
available to earlier Hadoop versions (pre 2.6). Therefore, for earlier Hadoop versions, the user needs to make
sure this configuration option is consistent with the Yarn setup.
ATM, it should be fine to keep this option 'false', because with the current
SlotManagerImpl all the
TM containers should have the same resources. If later we add another
SlotManager implementation that may
have TMs with different resources, and if we need it to work with pre 2.6 Hadoop versions, we can expose this
configuration option to users.
Copyright © 2014–2020 The Apache Software Foundation. All rights reserved.