You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/01/17 03:27:00 UTC
[jira] [Created] (YARN-10089) [Rollingupragde] PhysicalResource be
always null (RMNode should be updated NM registeration))
Brahma Reddy Battula created YARN-10089:
-------------------------------------------
Summary: [Rollingupragde] PhysicalResource be always null (RMNode should be updated NM registeration))
Key: YARN-10089
URL: https://issues.apache.org/jira/browse/YARN-10089
Project: Hadoop YARN
Issue Type: Bug
Reporter: Brahma Reddy Battula
PhysicalResource will be null always, in following scenario
i) Upgrade RM from 2.7 to 3.0.
ii) Upgrade NM from 2.7 to 3.0.
Here when NM re-register,as RMContext already have this nodeID so it will not added again as httpport also same hence "PhysicalResource" will be always null in the upgraded cluster till RM restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org