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] Updated: (MAPREDUCE-437) JobTracker must ask for a new FS instance and close it when terminated.
Date Sat, 12 Feb 2011 09:12:57 GMT

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

Steve Loughran updated MAPREDUCE-437:
-------------------------------------

           Component/s: jobtracker
     Affects Version/s: 0.23.0
                        0.22.0
                        0.20.1
                        0.21.0
              Assignee: Steve Loughran
    Remaining Estimate: 1.5h
     Original Estimate: 1.5h
               Summary: JobTracker must ask for a new FS instance and close it when terminated.
 (was: JobTracker may need to close its filesystem when being terminated)

changing title, marking versions it affects. Leaving as minor as this will not show up in
production if you start the JT in its own VM

> 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, 0.23.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>   Original Estimate: 1.5h
>  Remaining Estimate: 1.5h
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message