[
https://issues.apache.org/jira/browse/YARN-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225841#comment-16225841
]
Subru Krishnan commented on YARN-7371:
--------------------------------------
[~csingh]/[~billie.rinaldi], I am *not* in favor of replacing _allocationId_
with _priority_ as that's semantically incorrect. Moreover _allocationId_ was
added exactly to serve the purpose. So I suggest to instead add _allocationId_
in recovery. Thanks.
> NPE in ServiceMaster after RM is restarted and then the ServiceMaster is
> killed
> -------------------------------------------------------------------------------
>
> Key: YARN-7371
> URL: https://issues.apache.org/jira/browse/YARN-7371
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Attachments: YARN-7371-yarn-native-services.001.patch,
> YARN-7371-yarn-native-services.002.patch,
> YARN-7371-yarn-native-services.003.patch,
> YARN-7371-yarn-native-services.004.patch
>
>
> java.lang.NullPointerException
> at
> org.apache.hadoop.yarn.service.ServiceScheduler.recoverComponents(ServiceScheduler.java:313)
> at
> org.apache.hadoop.yarn.service.ServiceScheduler.serviceStart(ServiceScheduler.java:265)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
> at
> org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:121)
> at org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
> at org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:150)
> Steps:
> 1. Stopped RM and then started it
> 2. Application was still running
> 3. Killed the ServiceMaster to check if it recovers
> 4. Next attempt failed with the above exception
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
