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 "Eric Yang (JIRA)" <ji...@apache.org> on 2018/08/16 16:12:00 UTC

[jira] [Comment Edited] (YARN-8667) Container Relaunch fails with "find: File system loop detected;" for tar ball artifacts

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

Eric Yang edited comment on YARN-8667 at 8/16/18 4:11 PM:
----------------------------------------------------------

[~csingh] Thank you for the patch.  There is no need to pass container as a variable to cleanupContainerFiles because the code path from cleanupContainer depends on the global container variable.  The same variable doesn't change when protected void cleanupContainerFiles(Path containerWorkDir) method is reached.


was (Author: eyang):
[~csingh] Thank you for the patch.  There is no need to pass container as a variable to cleanupContainerFiles because the codel path from cleanupContainer depends on the global container variable.  The same variable doesn't change when protected void cleanupContainerFiles(Path containerWorkDir) method is reached.

> Container Relaunch fails with "find: File system loop detected;" for tar ball artifacts
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-8667
>                 URL: https://issues.apache.org/jira/browse/YARN-8667
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Rohith Sharma K S
>            Assignee: Chandni Singh
>            Priority: Major
>         Attachments: YARN-8667.001.patch
>
>
> Service is launched with TAR BALL artifacts. If a container is exited due to any reasons, container relaunch policy try to relaunch the container on same node with same container work space. As a result, container relaunch is keep on failing. 
> If container relaunch max-retry policy is disabled, then  container never launched in any other nodes also rather it keep on retrying on same node manager which never succeeds.
> {code}
> Relaunching Container container_e05_1533635581781_0001_01_000002. Remaining retry attempts(after relaunch) : -4816.
> {code}
> There are two issues
> # Container relaunch is keep on failing
> # Log message is misleading



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