[
https://issues.apache.org/jira/browse/HADOOP-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535249#comment-16535249
]
Hudson commented on HADOOP-15571:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14530 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14530/])
HADOOP-15571. Multiple FileContexts created with the same configuration (xyao:
rev 498e3bfb6b93bf542e5581d83e64e920983fe87e)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/AggregatedLogFormat.java
* (edit)
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestFileContext.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileContext.java
> Multiple FileContexts created with the same configuration object should be
> allowed to have different umask
> ----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15571
> URL: https://issues.apache.org/jira/browse/HADOOP-15571
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: HADOOP-15571.1.txt, HADOOP-15571.txt
>
>
> Ran into a super hard-to-debug issue due to this. [Edit: Turns out the same
> issue as YARN-5749 that [~Tao Yang] ran into]
> h4. Issue
> Configuration conf = new Configuration();
> fc1 = FileContext.getFileContext(uri1, conf);
> fc2 = FileContext.getFileContext(uri2, conf);
> fc.setUMask(umask_for_fc1); // Screws up umask for fc2 also!
> This was not the case before HADOOP-13440.
> h4. Symptoms:
> h5. Scenario I ran into
> When trying to localize a HDFS directory (hdfs:///my/dir/1.txt), NodeManager
> tries to replicate the directory structure on the local file-system
> ($yarn-local-dirs/filecache/my/dir/1.txt).
> Now depending on whether NM has ever done a log-aggregation (completely
> unrelated code that sets umask to be 137 for its own files on HDFS), the
> directories /my and /my/dir on local-fs may have different permissions. In
> the specific case where NM did log-aggregation, /my/dir was created with 137
> umask and so localization of 1.txt completely failed due to absent directory
> executable permissions!
> h5. Previous scenarios:
> We ran into this before in test-cases and instead of fixing the root-cause,
> we just fixed the test-cases: YARN-5679 / YARN-5749
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
