From yarn-issues-return-141140-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Mar 30 15:50:06 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 9F824180671 for ; Fri, 30 Mar 2018 15:50:05 +0200 (CEST) Received: (qmail 3491 invoked by uid 500); 30 Mar 2018 13:50:04 -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 3477 invoked by uid 99); 30 Mar 2018 13:50:04 -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; Fri, 30 Mar 2018 13:50:04 +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 0C9CCC0496 for ; Fri, 30 Mar 2018 13:50:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id b7HS01M1Go2t for ; Fri, 30 Mar 2018 13:50:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 67F015F5B0 for ; Fri, 30 Mar 2018 13:50:02 +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 39E94E0EFC for ; Fri, 30 Mar 2018 13:50:01 +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 5129C255FE for ; Fri, 30 Mar 2018 13:50:00 +0000 (UTC) Date: Fri, 30 Mar 2018 13:50:00 +0000 (UTC) From: "Shane Kumpf (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7973) Support ContainerRelaunch for Docker containers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7973?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16420= 505#comment-16420505 ]=20 Shane Kumpf commented on YARN-7973: ----------------------------------- Thanks for trying out the patch [~eyang]! {quote} Container relaunch is kind of working on my cluster using the examp= le above. If an app is stopped, and restarted, new containers would be acq= uired. If container fails, and the same one will be used for relaunch. {qu= ote} So it seems that there may be inconsistent use of the container relaunch po= licy in Native Services. That isn't really in scope for this patch, but sou= nds like something we should review in a separate issue. The only change in= flow is when a container transitions to the relaunching state and Docker i= s in use, so this patch doesn't change how Native Services leverages that t= ransition. {quote}However, I encountered a problem where flexing containers from 2 to = 3, then decrease back to 2. The flexing command failed to be received by A= M with the following error message{code} I haven't been able to recreate this. Based on the exception type, it looks= like the Services API may have been down? Can you share the RM and NM logs= when this happens? I really wouldn't expect this patch to be related to th= at exception as it doesn't touch the Services API. > Support ContainerRelaunch for Docker containers > ----------------------------------------------- > > Key: YARN-7973 > URL: https://issues.apache.org/jira/browse/YARN-7973 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Shane Kumpf > Assignee: Shane Kumpf > Priority: Major > Attachments: YARN-7973.001.patch, YARN-7973.002.patch > > > Prior to YARN-5366, {{container-executor}}=C2=A0would remove the Docker c= ontainer when it exited. The removal is now handled by the {{DockerLinuxCon= tainerRuntime}}. {{ContainerRelaunch}}=C2=A0is intended to reuse the workdi= r from the previous attempt, and does not call {{cleanupContainer}}=C2=A0pr= ior to {{launchContainer}}. The container ID is reused as well. As a result= , the previous Docker container still exists, resulting in an error from Do= cker indicating the a container by that name already exists. -- 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