hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-31) Have a better shutdown and cleanup mechanism in JobTracker
Date Sat, 31 Dec 2011 09:08:30 GMT

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

Harsh J resolved MAPREDUCE-31.
------------------------------

    Resolution: Not A Problem

This isn't a problem anymore on trunk. The JT has gone away and I do not think the MR2 components
suffer from the same.

Besides, I've not seen this happen on branch-1 either, but I was not looking very close.
                
> Have a better shutdown and cleanup mechanism in JobTracker
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-31
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-31
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amar Kamat
>
> The {{main()}} of JobTracker waits for {{offerSerice()}} to complete. {{offerService()}}
does a {{Thread.join()}} on {{interTrackerServer}}. 
> {{JobTracker.close()}} stops {{interTrackerServer}} pretty early and hence there is a
fair chance of JobTracker exiting before other threads are stopped _properly_.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message