From yarn-issues-return-136973-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Feb 1 17:22:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D04AA18066D for ; Thu, 1 Feb 2018 17:22:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C0D4D160C26; Thu, 1 Feb 2018 16:22:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15B8E160C44 for ; Thu, 1 Feb 2018 17:22:03 +0100 (CET) Received: (qmail 52995 invoked by uid 500); 1 Feb 2018 16:22: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 52979 invoked by uid 99); 1 Feb 2018 16:22:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2018 16:22:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BEDB01A675C for ; Thu, 1 Feb 2018 16:22:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HQHmJiaFarUh for ; Thu, 1 Feb 2018 16:22:02 +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 D33A15F4A8 for ; Thu, 1 Feb 2018 16:22: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 20118E0309 for ; Thu, 1 Feb 2018 16:22: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 5614422D07 for ; Thu, 1 Feb 2018 16:22:00 +0000 (UTC) Date: Thu, 1 Feb 2018 16:22:00 +0000 (UTC) From: "Jason Lowe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7677) Docker image cannot set HADOOP_CONF_DIR 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-7677?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16348= 841#comment-16348841 ]=20 Jason Lowe commented on YARN-7677: ---------------------------------- Ultimately one way to debug this would be to compare the container launch s= cripts between the two scenarios (i.e.: with and without YARN-7677 applied)= .=C2=A0 The only difference should be that some variables in the launch scr= ipt will have the export var=3D$\{_var_:-_value_\} syntax that didn't befor= e. In the non-Docker case, all of those variables should be getting the NM= settings unless somehow those variables already are set to _different_ val= ues in the environment before the launch script runs. > Docker image cannot set HADOOP_CONF_DIR > --------------------------------------- > > Key: YARN-7677 > URL: https://issues.apache.org/jira/browse/YARN-7677 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Eric Badger > Assignee: Jim Brennan > Priority: Major > Fix For: 3.1.0, 3.0.1 > > Attachments: YARN-7677.001.patch, YARN-7677.002.patch > > > Currently, {{HADOOP_CONF_DIR}} is being put into the task environment whe= ther it's set by the user or not. It completely bypasses the whitelist and = so there is no way for a task to not have {{HADOOP_CONF_DIR}} set. This cau= ses problems in the Docker use case where Docker containers will set up the= ir own environment and have their own {{HADOOP_CONF_DIR}} preset in the ima= ge itself.=20 -- 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