[
https://issues.apache.org/jira/browse/HADOOP-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala resolved HADOOP-4919.
--------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
I just committed this to the 0.18 branch (for Hadoop 0.18.3). Thanks, Peeyush !
> [HOD] Provide execute access to JT history directory path for group
> -------------------------------------------------------------------
>
> Key: HADOOP-4919
> URL: https://issues.apache.org/jira/browse/HADOOP-4919
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Reporter: Hemanth Yamijala
> Assignee: Peeyush Bishnoi
> Fix For: 0.18.3
>
> Attachments: hadoop-4919.txt
>
>
> HADOOP-4782 was opened to discuss the right level of access required for
> Chukwa to be able to read JT history logs under HOD provisioned directories.
> This was in turn required because HADOOP-4705, which provided world readable
> rights for all directories provisioned by HOD was found to be very unsecure
> for shared clusters. As per discussions on these two jiras, we decided to NOT
> change HOD's default behavior (of not granting access) for Hadoop 0.20, and
> providing very restricted access for Hadoop 0.18.3 (only execute permissions
> for group on the directory path until the history directory on the JT node).
> HADOOP-4782 tracked the reversal of the changes in HADOOP-4705 for Hadoop
> 0.20. This issue is being opened to make the restricted change in Hadoop
> 0.18.3. The patch submitted on HADOOP-4782 for Hadoop 0.18.3 can just be
> uploaded here. I am filing a new jira only because the nature of the fixes is
> different in spirit for the two versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
