[
https://issues.apache.org/jira/browse/YARN-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-7454:
-----------------------------
Attachment: YARN-7454.001.patch
Attaching a patch that avoids the double app lookup, adds a null check in case
the app doesn't have an active attempt, and avoids a double-lookup in the
attempt's resource usage map.
> RMAppAttemptMetrics#getAggregateResourceUsage can NPE due to double lookup
> --------------------------------------------------------------------------
>
> Key: YARN-7454
> URL: https://issues.apache.org/jira/browse/YARN-7454
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Jason Lowe
> Priority: Minor
> Attachments: YARN-7454.001.patch
>
>
> RMAppAttemptMetrics#getAggregateResourceUsage does a double-lookup on a
> concurrent hash map, but the app could be removed from the map between the
> two lookups:
> {code}
> RMApp rmApp = rmContext.getRMApps().get(attemptId.getApplicationId());
> if (rmApp != null) {
> RMAppAttempt currentAttempt =
> rmContext.getRMApps().get(attemptId.getApplicationId()).getCurrentAppAttempt();
> {code}
> The attempt should be looked up within rmApp directly rather than redundantly
> trying to retrieve the RMApp first.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
