[jira] [Updated] (YARN-1849) NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters
[ https://issues.apache.org/jira/browse/YARN-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1849: --- Attachment: yarn-1849-3.patch Test failure is unrelated. New patch fixes javac warning. > NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters > > > Key: YARN-1849 > URL: https://issues.apache.org/jira/browse/YARN-1849 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Blocker > Attachments: yarn-1849-1.patch, yarn-1849-2.patch, yarn-1849-2.patch, > yarn-1849-3.patch > > > While running an UnmanagedAM on secure cluster, ran into an NPE on > failover/restart. This is similar to YARN-1821. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (YARN-1849) NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters
[ https://issues.apache.org/jira/browse/YARN-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1849: --- Attachment: yarn-1849-2.patch Cosmetic import fix. > NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters > > > Key: YARN-1849 > URL: https://issues.apache.org/jira/browse/YARN-1849 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Blocker > Attachments: yarn-1849-1.patch, yarn-1849-2.patch, yarn-1849-2.patch > > > While running an UnmanagedAM on secure cluster, ran into an NPE on > failover/restart. This is similar to YARN-1821. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (YARN-1849) NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters
[ https://issues.apache.org/jira/browse/YARN-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1849: --- Attachment: yarn-1849-2.patch Thinking more, thought we could benefit from better logging for the various null cases even if we are ignoring all of them. The new patch does that and factors handling the ContainerStatus to a different method. > NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters > > > Key: YARN-1849 > URL: https://issues.apache.org/jira/browse/YARN-1849 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Blocker > Attachments: yarn-1849-1.patch, yarn-1849-2.patch > > > While running an UnmanagedAM on secure cluster, ran into an NPE on > failover/restart. This is similar to YARN-1821. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (YARN-1849) NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters
[ https://issues.apache.org/jira/browse/YARN-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1849: --- Attachment: yarn-1849-1.patch > NPE in ResourceTrackerService#registerNodeManager for UAM on secure clusters > > > Key: YARN-1849 > URL: https://issues.apache.org/jira/browse/YARN-1849 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Karthik Kambatla >Assignee: Karthik Kambatla >Priority: Blocker > Attachments: yarn-1849-1.patch > > > While running an UnmanagedAM on secure cluster, ran into an NPE on > failover/restart. This is similar to YARN-1821. -- This message was sent by Atlassian JIRA (v6.2#6252)
