From yarn-issues-return-151398-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Aug 15 21:38:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DC79F180626 for ; Wed, 15 Aug 2018 21:38:03 +0200 (CEST) Received: (qmail 94726 invoked by uid 500); 15 Aug 2018 19:38:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 94715 invoked by uid 99); 15 Aug 2018 19:38:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2018 19:38:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7356EC06B7 for ; Wed, 15 Aug 2018 19:38:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 3OUIaJEmvYka for ; Wed, 15 Aug 2018 19:38:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A3FE95F1A1 for ; Wed, 15 Aug 2018 19:38:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D9F57E12FE for ; Wed, 15 Aug 2018 19:38:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3C2D123F9D for ; Wed, 15 Aug 2018 19:38:00 +0000 (UTC) Date: Wed, 15 Aug 2018 19:38:00 +0000 (UTC) From: "Chandni Singh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8667) Container Relaunch fails with "find: File system loop detected;" for tar ball artifacts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581524#comment-16581524 ] Chandni Singh commented on YARN-8667: ------------------------------------- Before relaunch, container script and container tokens file is deleted from the container's working directory. {code:java} protected void cleanupContainerFiles(Path containerWorkDir) { LOG.debug("cleanup container {} files", containerWorkDir); // delete ContainerScriptPath deleteAsUser(new Path(containerWorkDir, CONTAINER_SCRIPT)); // delete TokensPath deleteAsUser(new Path(containerWorkDir, FINAL_CONTAINER_TOKENS_FILE)); }{code} Seems like we might have to delete any symlinks from the container's working directory as well? cc. [~billie.rinaldi] [~shanekumpf@gmail.com] [~eyang] > 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 > > 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