From common-issues-return-154372-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Jul 2 19:44: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 3E056180674 for ; Mon, 2 Jul 2018 19:44:04 +0200 (CEST) Received: (qmail 35139 invoked by uid 500); 2 Jul 2018 17:44:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 35128 invoked by uid 99); 2 Jul 2018 17:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul 2018 17:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B46A5CD357 for ; Mon, 2 Jul 2018 17:44:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id EqBtiPk8mBj0 for ; Mon, 2 Jul 2018 17:44:02 +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 A8F1C5F3BC for ; Mon, 2 Jul 2018 17:44: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 DBE27E105A for ; Mon, 2 Jul 2018 17:44: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 4596D21843 for ; Mon, 2 Jul 2018 17:44:00 +0000 (UTC) Date: Mon, 2 Jul 2018 17:44:00 +0000 (UTC) From: "Xiaoyu Yao (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-15571) After HADOOP-13440, multiple filesystems/file-contexts created with the same Configuration object are forced to have the same umask 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/HADOOP-15571?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 530232#comment-16530232 ]=20 Xiaoyu Yao commented on HADOOP-15571: ------------------------------------- {quote}That was my first approach too, but there are too many uses of FileC= ontext (in YARN and potentially as well as in downstream projects) and forc= ing all of them to create a new Configuration object is not right. This cre= ation of such a new Config object per URI was not needed in 2.x. {quote} [~vinodkv], that makes sense to me. +1 for adding a regression test for the= fix.=C2=A0 =C2=A0 > After HADOOP-13440, multiple filesystems/file-contexts created with the s= ame Configuration object are forced to have the same umask > -------------------------------------------------------------------------= ---------------------------------------------------------- > > Key: HADOOP-15571 > URL: https://issues.apache.org/jira/browse/HADOOP-15571 > Project: Hadoop Common > Issue Type: Bug > Reporter: Vinod Kumar Vavilapalli > Assignee: Vinod Kumar Vavilapalli > Priority: Critical > Attachments: HADOOP-15571.txt > > > Ran into a super hard-to-debug issue due to this. [Edit: Turns out the sa= me issue as YARN-5749 that [~Tao Yang] ran into] > h4. Issue > Configuration conf =3D new Configuration(); > fc1 =3D FileContext.getFileContext(uri1, conf); > fc2 =3D FileContext.getFileContext(uri2, conf); > fc.setUMask(umask_for_fc1); // Screws up umask for fc2 also! > This was not the case before HADOOP-13440. > h4. Symptoms: > h5. Scenario I ran into > When trying to localize a HDFS directory (hdfs:///my/dir/1.txt), NodeMana= ger tries to replicate the directory structure on the local file-system ($y= arn-local-dirs/filecache/my/dir/1.txt). > Now depending on whether NM has ever done a log-aggregation (completely u= nrelated code that sets umask to be 137 for its own files on HDFS), the dir= ectories /my and /my/dir on local-fs may have different permissions. In the= specific case where NM did log-aggregation, /my/dir was created with 137 u= mask and so localization of 1.txt completely failed due to absent directory= executable permissions! > h5. Previous scenarios: > We ran into this before in test-cases and instead of fixing the root-caus= e, we just fixed the test-cases: YARN-5679 / YARN-5749 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org