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 "Xuan Gong (JIRA)" <ji...@apache.org> on 2013/07/23 02:14:49 UTC
[jira] [Commented] (YARN-770) NPE NodeStatusUpdaterImpl
[ https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715895#comment-13715895 ]
Xuan Gong commented on YARN-770:
--------------------------------
[~stevel@apache.org] Could you provide me more information that I can re-produce this error, such as which command you are running ?
I do not think this
<code>
//get next heartbeat interval from response
nextHeartBeatInterval = response.getNextHeartBeatInterval();
</code>
will cause this issue.
Because at ResourceTrackerService, this is how the response will be initiated before it returns back
<code>
NodeHeartbeatResponse nodeHeartBeatResponse = YarnServerBuilderUtils
.newNodeHeartbeatResponse(lastNodeHeartbeatResponse.
getResponseId() + 1, NodeAction.NORMAL, null, null, null, null,
nextHeartBeatInterval);
</code>. The nextHeartBeatInterval will be set.
> NPE NodeStatusUpdaterImpl
> -------------------------
>
> Key: YARN-770
> URL: https://issues.apache.org/jira/browse/YARN-770
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Priority: Minor
>
> A mini yarn cluster based test just failed -NPE in the logs in {{NodeStatusUpdaterImpl}}, which is probably a symptom of the problem, not the cause -network trouble more likely there- but it shows there's some extra checking for null responses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira