[ https://issues.apache.org/jira/browse/YARN-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666590#comment-15666590 ]
Varun Saxena commented on YARN-5287: ------------------------------------ [~brahmareddy] IIUC, we now use individual JIRAs' to build release notes. YARN-5765 is already there which can be used to track the revert. Which is similar to what has been done for YARN-5882 (which will be used to track revert of YARN-4126). While reverting YARN-5287, YARN-5765 has been mentioned in the commit message. The only thing which needs to be done is close that JIRA and mark fix version as 3.0.0-alpha2. Shouldn't that be enough ? Thoughts ? > LinuxContainerExecutor fails to set proper permission > ----------------------------------------------------- > > Key: YARN-5287 > URL: https://issues.apache.org/jira/browse/YARN-5287 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.7.2 > Reporter: Ying Zhang > Assignee: Naganarasimha G R > Priority: Minor > Fix For: 2.8.0, 3.0.0-alpha1 > > Attachments: YARN-5287-tmp.patch, YARN-5287.003.patch, > YARN-5287.004.patch, YARN-5287.005.patch, YARN-5287.branch-2.001.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > LinuxContainerExecutor fails to set the proper permissions on the local > directories(i.e., /hadoop/yarn/local/usercache/... by default) if the cluster > has been configured with a restrictive umask, e.g.: umask 077. Job failed due > to the following reason: > Path /hadoop/yarn/local/usercache/ambari-qa/appcache/application_xxxxxxxx has > permission 700 but needs permission 750 -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org