hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-437) JobTracker must ask for a new FS instance and close it when terminated.
Date Mon, 03 Mar 2014 10:07:21 GMT

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

Steve Loughran resolved MAPREDUCE-437.
--------------------------------------

    Resolution: Cannot Reproduce

implicitly fixed post YARN as the JT is dynamically created in its own process

> JobTracker must ask for a new FS instance and close it when terminated.
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-437
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-437
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.1, 0.21.0, 0.22.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>             Fix For: 0.22.1
>
>         Attachments: MAPREDUCE-437.patch
>
>   Original Estimate: 1.5h
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> This is something I've been experimenting with HADOOP-3268; I'm not sure what the right
action is here.
> -currently, the JobTracker does not close() its filesystem when it is shut down. This
will cause it to leak filesystem references if JobTrackers are started and stopped in the
same process.
> -The TestMRServerPorts test explicitly closes the filesystem
>         jt.fs.close();
>         jt.stopTracker();
> -If you move the close() operation into the stopTracker()/terminate logic, the filesystem
gets cleaned up, but 
> TestRackAwareTaskPlacement and TestMultipleLevelCaching fail with a FilesystemClosed
error (stack traces to follow)
> Should the JobTracker close its filesystem whenever it is terminated? If so, there are
some tests that need to be reworked slightly to not expect the fileystem to be live after
the jobtracker is taken down.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message