Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1201634722.1231213904369.JavaMail.jira@brutus>
Date: Mon, 5 Jan 2009 19:51:44 -0800 (PST)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4783) History files are given world
 readable permissions.
In-Reply-To: <770038609.1228463806250.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala updated HADOOP-4783:
-------------------------------------

    Priority: Blocker  (was: Major)

Yes, I think it should be a blocker. Marking as such.

> History files are given world readable permissions.
> ---------------------------------------------------
>
>                 Key: HADOOP-4783
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4783
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Hemanth Yamijala
>            Priority: Blocker
>
> It is found that history files are being created with permissions 0777. On shared clusters this is opening up too much. However, there is a requirement to allow Chukwa to read history files. (See HADOOP-4705). This issue is to set up appropriate permissions for the files to be as restrictive as required, while still fixing the problem for Chukwa.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.