hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-515) Node Manager not getting the master key
Date Mon, 01 Apr 2013 18:07:16 GMT

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

Siddharth Seth commented on YARN-515:
-------------------------------------

Missed this while reviewing YARN-440... also in the second (probably biased) review when this
jira was opened. Sorry about that.

bq. I just think all this extra code to try and wrap the protocol buffers is just a bad idea.
It makes things difficult to change a .proto file
Agree with this. Seemed useful at the time, but the PBImpl stuff is rather painful to maintain,
without adding a whole lot of value.
                
> Node Manager not getting the master key
> ---------------------------------------
>
>                 Key: YARN-515
>                 URL: https://issues.apache.org/jira/browse/YARN-515
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.4-alpha
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>             Fix For: 2.0.5-beta
>
>         Attachments: YARN-515.txt
>
>
> On branch-2 the latest version I see the following on a secure cluster.
> {noformat}
> 2013-03-28 19:21:06,243 [main] INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl:
Security enabled - updating secret keys now
> 2013-03-28 19:21:06,243 [main] INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl:
Registered with ResourceManager as RM:PORT with total resource of <me
> mory:12288, vCores:16>
> 2013-03-28 19:21:06,244 [main] INFO org.apache.hadoop.yarn.service.AbstractService: Service:org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl
is started.
> 2013-03-28 19:21:06,245 [main] INFO org.apache.hadoop.yarn.service.AbstractService: Service:org.apache.hadoop.yarn.server.nodemanager.NodeManager
is started.
> 2013-03-28 19:21:07,257 [Node Status Updater] ERROR org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl:
Caught exception in status-updater
> java.lang.NullPointerException
>         at org.apache.hadoop.yarn.server.security.BaseContainerTokenSecretManager.getCurrentKey(BaseContainerTokenSecretManager.java:121)
>         at org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl$1.run(NodeStatusUpdaterImpl.java:407)
> {noformat}
> The Null pointer exception just keeps repeating and all of the nodes end up being lost.
 It looks like it never gets the secret key when it registers.

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

Mime
View raw message