hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6801) NPE in RM while setting collectors map in NodeHeartbeatResponse
Date Tue, 11 Jul 2017 06:48:02 GMT

    [ https://issues.apache.org/jira/browse/YARN-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081761#comment-16081761
] 

Vrushali C commented on YARN-6801:
----------------------------------

It's interesting, it's not during the upgrade. It's when there are several app submissions
on the RM. I saw this on our test cluster. It does not seem to happen very often. This happens
during the small time window when there is an app id but no app object yet. 


> NPE in RM while setting collectors map in NodeHeartbeatResponse
> ---------------------------------------------------------------
>
>                 Key: YARN-6801
>                 URL: https://issues.apache.org/jira/browse/YARN-6801
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-5355, YARN-5355-branch-2
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>         Attachments: YARN-6801-YARN-5355.001.patch
>
>
> Null Pointer Exception seen in ResourceTrackerService#setAppCollectorsMapToResponse call

> {code}
> 2017-06-22 22:24:01,437 WARN org.apache.hadoop.ipc.Server: IPC Server handler 49 on 8031,
call org.apache.hadoop.yarn.server.api.ResourceTrackerPB.nodeHeartbeat from 10.35.172.116:44399
Call#3929 Retry#0
> java.lang.NullPointerException
>         at org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService.setAppCollectorsMapToResponse(ResourceTrackerService.java:467)
>         at org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService.nodeHeartbeat(ResourceTrackerService.java:447)
>         at org.apache.hadoop.yarn.server.api.impl.pb.service.ResourceTrackerPBServiceImpl.nodeHeartbeat(ResourceTrackerPBServiceImpl.java:68)
>         at org.apache.hadoop.yarn.proto.ResourceTracker$ResourceTrackerService$2.callBlockingMethod(ResourceTracker.java:81)
>         at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:619)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:962)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2084)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2080)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Subject.java:415)
>         at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1645)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2078)
> {code}
> It correlates to RM invoking setAppCollectorsMapToResponse and calling 
> {code}
>       AppCollectorData appCollectorData = rmApps.get(appId).getCollectorData();
> {code}
> If the app object is not present in the list of running app ids, then this will throw
NPE.
> Filing jira to fix it. 



--
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


Mime
View raw message