[
https://issues.apache.org/jira/browse/MAPREDUCE-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348884#comment-14348884
]
Hudson commented on MAPREDUCE-6136:
-----------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #123 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/123/])
MAPREDUCE-6136. MRAppMaster doesn't shutdown file systems. Contributed by
Brahma Reddy Battula. (ozawa: rev 348208014b2023894dc416dcd733a9ccdafc6e25)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
* hadoop-mapreduce-project/CHANGES.txt
> MRAppMaster doesn't shutdown file systems
> -----------------------------------------
>
> Key: MAPREDUCE-6136
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6136
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 2.4.1, 2.6.0
> Reporter: Noah Watkins
> Assignee: Brahma Reddy Battula
> Fix For: 2.7.0
>
> Attachments: MAPRED-6136.patch
>
>
> When MRAppMaster exit it doesn't call close on its open file systems
> instances.
> MAPREDUCE-3614 sets conf.setBoolean("fs.automatic.close", false); in
> MRAppMaster::main and then called FileSystem.closeAll() in
> MRAppMasterShutdownHook.
> However, MAPREDUCE-4205 removed the call to FileSystem.closeAll()
> MRAppMasterShutdownHook but left `fs.automatic.close` set to false.
> Removing `conf.setBoolean("fs.automatic.close", false);` worked for me, but
> it wasn't clear if this had other implications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
