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 "Rohith (JIRA)" <ji...@apache.org> on 2014/04/12 09:51:15 UTC
[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore
caused by handling Disconnected event from ZK.
[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967437#comment-13967437 ]
Rohith commented on YARN-1934:
------------------------------
Call flow is attached file issue is
1. Disconnected event which made *zkClient=null*.
2. Call for ZKRMStateStore.updateApplicationAttemptStateInternal() from RMAppAttemptImpl.(EXPIRED event not yet come).
> Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.
> ------------------------------------------------------------------------------
>
> Key: YARN-1934
> URL: https://issues.apache.org/jira/browse/YARN-1934
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Rohith
> Priority: Critical
> Attachments: RM.txt
>
>
> For ZK disconnected event , zkClient is set to null. It is very much prone to throw NPE.
> {noformat}
> case Disconnected:
> LOG.info("ZKRMStateStore Session disconnected");
> oldZkClient = zkClient;
> zkClient = null;
> break;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)