[
https://issues.apache.org/jira/browse/BIGTOP-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810338#comment-13810338
]
Aaron T. Myers commented on BIGTOP-1050:
----------------------------------------
Certainly doesn't need to be fixed urgently, as there's no material difference
in functionality. The thing that bugs me about this is that we currently treat
the permissions for the LTC and LCE differently, both in documentation and
packaging/deployment scripts. There's no good reason for that, and it
complicates the situation a bit.
> Permissions on YARN LCE should be 4754
> --------------------------------------
>
> Key: BIGTOP-1050
> URL: https://issues.apache.org/jira/browse/BIGTOP-1050
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments:
> 0001-BIGTOP-1050.-Permissions-on-YARN-LCE-should-be-4754.patch
>
>
> The permissions we set for the YARN container executor are not exactly
> correct and are different from what we used to set for the MRv1 task
> containers. The requirements for the permissions are as follows:
> * Readable/executable by the group
> * Not executable by others
> * Not writable by others
> * Set UID
> * Owned by root
> I've tested this in YARN and have tested that I can still submit and run jobs
> successfully with these new permissions. This is somewhat second-hand
> information, so I'll CC [~atm] in case I've missed any important details or
> context...
--
This message was sent by Atlassian JIRA
(v6.1#6144)
