Szilard Nemeth created YARN-9024:
------------------------------------
Summary: ClusterNodeTracker maximum allocation does not respect
resource units
Key: YARN-9024
URL: https://issues.apache.org/jira/browse/YARN-9024
Project: Hadoop YARN
Issue Type: Bug
Reporter: Szilard Nemeth
Assignee: Szilard Nemeth
If a custom resource is defined with a default unit value (base unit) and a
node reports its total capability in a different unit (e.g. M) then
{{ClusterNodeTracker.getMaxAllowedAllocation}} returns the max allocation
resource in the base unit, so the reported resource unit is not respected.
The issue is when the \{{updateMaxResources}} method is called (i.e. NM node is
registered), the unit of the node's resources is not checked. In this method,
we need to convert the reported value to the unit defined by RM for the
individual resource types.
I also wanted to add a testcase where memory has G as its unit, but it was not
possible easily without hacky code so I only added a testcase that verifies
custom resource values.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
