[
https://issues.apache.org/jira/browse/YARN-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297713#comment-16297713
]
Eric Yang commented on YARN-7565:
---------------------------------
I get a null pointer exception like this:
{code}
2017-12-20 00:07:47,079 [main] INFO service.AbstractService - Service aaa
failed in state STARTED; cause: java.lang.NullPointerException
java.lang.NullPointerException
at
java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at
java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at
org.apache.hadoop.yarn.service.ServiceScheduler.lambda$recoverComponents$0(ServiceScheduler.java:360)
at java.util.HashMap.forEach(HashMap.java:1288)
at
org.apache.hadoop.yarn.service.ServiceScheduler.recoverComponents(ServiceScheduler.java:352)
at
org.apache.hadoop.yarn.service.ServiceScheduler.serviceStart(ServiceScheduler.java:292)
at
org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at
org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:121)
at
org.apache.hadoop.yarn.service.ServiceMaster.lambda$serviceStart$0(ServiceMaster.java:251)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1962)
at
org.apache.hadoop.yarn.service.ServiceMaster.serviceStart(ServiceMaster.java:249)
at
org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at
org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:320)
{code}
It looks like there is a problem that the code logic that compInstance is
trying to resolve based on record.description. Shouldn't compInstance base on
container name?
> Yarn service pre-maturely releases the container after AM restart
> ------------------------------------------------------------------
>
> Key: YARN-7565
> URL: https://issues.apache.org/jira/browse/YARN-7565
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Fix For: 3.1.0
>
> Attachments: YARN-7565.001.patch, YARN-7565.002.patch,
> YARN-7565.003.patch, YARN-7565.004.patch, YARN-7565.005.patch,
> YARN-7565.addendum.001.patch
>
>
> With YARN-6168, recovered containers can be reported to AM in response to the
> AM heartbeat.
> Currently, the Service Master will release the containers, that are not
> reported in the AM registration response, immediately.
> Instead, the master can wait for a configured amount of time for the
> containers to be recovered by RM. These containers are sent to AM in the
> heartbeat response. Once a container is not reported in the configured
> interval, it can be released by the master.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
