Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4AB18D971 for ; Tue, 23 Oct 2012 09:53:16 +0000 (UTC) Received: (qmail 67948 invoked by uid 500); 23 Oct 2012 09:53:15 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 67831 invoked by uid 500); 23 Oct 2012 09:53:13 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 67778 invoked by uid 99); 23 Oct 2012 09:53:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 09:53:12 +0000 Date: Tue, 23 Oct 2012 09:53:12 +0000 (UTC) From: "Ivan Mitic (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <797249881.15236.1350985992662.JavaMail.jiratomcat@arcas> In-Reply-To: <556339847.2085.1346088967901.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HADOOP-8731) Public distributed cache support for Windows 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/HADOOP-8731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482238#comment-13482238 ] Ivan Mitic commented on HADOOP-8731: ------------------------------------ Thanks a lot Vinod, Bikas for additional clarifications! I looked thru the codebase and things add up now :) As you pointed out, this is only a problem if the default file system is LFS and we pass in file:/// URI. This is the case in TestTrackerDistributedCacheManager hence the test fails. Would it still make sense to go with my fix (I still have to polish it up and address comments), or you'd like to look for alternative ways to only fix the test? > Public distributed cache support for Windows > -------------------------------------------- > > Key: HADOOP-8731 > URL: https://issues.apache.org/jira/browse/HADOOP-8731 > Project: Hadoop Common > Issue Type: Bug > Components: filecache > Reporter: Ivan Mitic > Assignee: Ivan Mitic > Attachments: HADOOP-8731-PublicCache.patch > > > A distributed cache file is considered public (sharable between MR jobs) if OTHER has read permissions on the file and +x permissions all the way up in the folder hierarchy. By default, Windows permissions are mapped to "700" all the way up to the drive letter, and it is unreasonable to ask users to change the permission on the whole drive to make the file public. IOW, it is hardly possible to have public distributed cache on Windows. > To enable the scenario and make it more "Windows friendly", the criteria on when a file is considered public should be relaxed. One proposal is to check whether the user has given EVERYONE group permission on the file only (and discard the +x check on parent folders). > Security considerations for the proposal: Default permissions on Unix platforms are usually "775" or "755" meaning that OTHER users can read and list folders by default. What this also means is that Hadoop users have to explicitly make the files private in order to make them private in the cluster (please correct me if this is not the case in real life!). On Windows, default permissions are "700". This means that by default all files are private. In the new model, if users want to make them public, they have to explicitly add EVERYONE group permissions on the file. > TestTrackerDistributedCacheManager fails because of this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira