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 "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2018/01/10 05:37:00 UTC
[jira] [Comment Edited] (YARN-7508) NPE in FiCaSchedulerApp when
debug log enabled in async-scheduling mode
[ https://issues.apache.org/jira/browse/YARN-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318505#comment-16318505 ]
Bibin A Chundatt edited comment on YARN-7508 at 1/10/18 5:36 AM:
-----------------------------------------------------------------
Committed to trunk ,branch-3 ,branch-2 and branch-2.9
was (Author: bibinchundatt):
Committed to trunk ,branch-3 and branch-2.9
> NPE in FiCaSchedulerApp when debug log enabled in async-scheduling mode
> -----------------------------------------------------------------------
>
> Key: YARN-7508
> URL: https://issues.apache.org/jira/browse/YARN-7508
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.9.0, 3.0.0-alpha4
> Reporter: Tao Yang
> Assignee: Tao Yang
> Fix For: 3.1.0, 2.10.0, 2.9.1, 3.0.1
>
> Attachments: YARN-7508.001.patch
>
>
> YARN-6678 have fixed the IllegalStateException problem but the debug log it added may cause NPE when trying to print containerId of non-existed reserved container on this node. Replace {{schedulerContainer.getSchedulerNode().getReservedContainer().getContainerId()}} with {{schedulerContainer.getSchedulerNode().getReservedContainer()}} can fix this problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org