You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Tsuyoshi Ozawa (JIRA)" <ji...@apache.org> on 2015/03/01 12:40:05 UTC

[jira] [Updated] (MAPREDUCE-6136) MRAppMaster doesn't shutdown file systems

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsuyoshi Ozawa updated MAPREDUCE-6136:
--------------------------------------
    Affects Version/s: 2.6.0

> 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
>
> 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)