[
https://issues.apache.org/jira/browse/YARN-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373186#comment-15373186
]
Inigo Goiri commented on YARN-5356:
-----------------------------------
[~nroberts], I think that changing machine resources it's not that common and
admins could always restart the Node Manager. in that case, I would just extend
{{RegisterNodeManagerRequestProto}} in
{{yarn_server_common_service_protos.proto}} and populate it in
{{NodeStatusUpdaterImpl#registerWithRM()}}. If we don't care about reporting
network, then adding {{Resource}} is fine. However, if we go into network and
disk, {{ResourceUtilization}} has those fields but I don't think that the
semantics we want to provide matches with resource utilization.
I can post a patch with these changes if you want.
> ResourceUtilization should also include resource availability
> -------------------------------------------------------------
>
> Key: YARN-5356
> URL: https://issues.apache.org/jira/browse/YARN-5356
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager, resourcemanager
> Affects Versions: 3.0.0-alpha1
> Reporter: Nathan Roberts
>
> Currently ResourceUtilization contains absolute quantities of resource used
> (e.g. 4096MB memory used). It would be good if it also included how much of
> that resource is actually available on the node so that the RM can use this
> data to schedule more effectively (overcommit, etc)
> Currently the only available information is the Resource the node registered
> with (or later updated using updateNodeResource). However, these aren't
> really sufficient to get a good view of how utilized a resource is. For
> example, if a node reports 400% CPU utilization, does that mean it's
> completely full, or barely utilized? Today there is no reliable way to figure
> this out.
> [~elgoiri] - Lots of good work is happening in YARN-2965 so curious if you
> have thoughts/opinions on this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
