[
https://issues.apache.org/jira/browse/YARN-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123782#comment-16123782
]
Wangda Tan commented on YARN-6789:
----------------------------------
[~vvasudev],
I was wondering if unit is a must-to-have field since unit will significantly
increase complexity. The example you provided is a good example, I think we
need it. So we need to get solutions to properly handle rolling upgrade.
There're several upgrade scenarios in my mind:
Case a: Old client/daemon (use old binary without YARN-3926) talk to new YARN
daemon (use new binary with YARN-3926).
Case b: New client/daemon talk to new YARN daemon, and units inside YARN daemon
is changed.
For #a, we need to add logic in Resource initialization part, when a unit is
not set by old client/daemon, server will set a default unit for these
resources.
For #b, if a unit is set by client/daemon, we will use it. If a unit is not
set, similar to above, server will set a default unit for these resources.
To support this, Resource object in YARN should be able to get if a unit is
empty ("") or null, and default unit will be returned with ResourceTypeInfo.
cc: [~sunilg]/[~templedf] for suggestions.
> new api to get all supported resources from RM
> ----------------------------------------------
>
> Key: YARN-6789
> URL: https://issues.apache.org/jira/browse/YARN-6789
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: YARN-6789-YARN-3926.001.patch
>
>
> It will be better to provide an api to get all supported resource types from
> RM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
