[
https://issues.apache.org/jira/browse/MAPREDUCE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805878#action_12805878
]
Vinod K V commented on MAPREDUCE-437:
-------------------------------------
+1 for the solution #2. I think this should be THE general pattern in all the
services, but guess fixing that's a superset of this issue...
> JobTracker may need to close its filesystem when being terminated
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-437
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-437
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Steve Loughran
> Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.
