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 "Chandni Singh (JIRA)" <ji...@apache.org> on 2018/12/01 00:59:00 UTC

[jira] [Commented] (YARN-9071) NM and service AM don't have updated status for reinitialized containers

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

Chandni Singh commented on YARN-9071:
-------------------------------------

There still seems to be an issue with updating the ip on the NM. Once container monitoring restarts, there looks like an exception:
{code}
2018-11-30 16:39:44,983 WARN  monitor.ContainersMonitorImpl (ContainersMonitorImpl.java:run(489)) - Uncaught exception in ContainersMonitorImpl while monitoring resource of  container_e71_1543596052785_0019_01_000002
{code}
This prevents fetching the IP.


> NM and service AM don't have updated status for reinitialized containers
> ------------------------------------------------------------------------
>
>                 Key: YARN-9071
>                 URL: https://issues.apache.org/jira/browse/YARN-9071
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Billie Rinaldi
>            Assignee: Chandni Singh
>            Priority: Critical
>         Attachments: YARN-9071.001.patch, YARN-9071.002.patch, YARN-9071.003.patch
>
>
> Container resource monitoring is not stopped during the reinitialization process, and this prevents the NM from obtaining updated process tree information when the container starts running again. I observed a reinitialized container go from RUNNING to REINITIALIZING to REINITIALIZING_AWAITING_KILL to SCHEDULED to RUNNING. Container monitoring was then started for a second time, but since the trackingContainers entry had already been initialized for the container, ContainersMonitor skipped finding the new PID and IP for the container. A possible solution would be to stop the container monitoring in the reinitialization process so that the process tree information would be initialized properly when monitoring is restarted. When the same container was stopped by the NM later, the NM did not kill the container, and the service AM received an unexpected event (stop at reinitializing).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org