[
https://issues.apache.org/jira/browse/MAPREDUCE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101108#comment-13101108
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2949:
----------------------------------------------------
bq. As part of this, the ResourceLocalizationService is initialized , which
starts PublicLocalizer Thread.
This is the bug that should be fixed. The service lifecycle clearly intends
{{init()}} to only initialize services. Threads should be started only via
{{start()}} so that {{stop()}} can properly handle their exit. We should just
make _ResourceLocalizationService.LocalizerTracker_ itself a service and follow
the above life-cycle pattern.
Can you look at your thread dump and name the other threads that are hanging
like this? Thanks!
> NodeManager in a inconsistent state if a service startup fails.
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-2949
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2949
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.24.0
> Reporter: Ravi Teja Ch N V
> Assignee: Ravi Teja Ch N V
>
> When a service startup fails at the Nodemanager, the Nodemanager JVM doesnot
> exit as the following threads are still running.
> Daemon Thread [Timer for 'NodeManager' metrics system] (Running)
> Thread [pool-1-thread-1] (Running)
> Thread [Thread-11] (Running)
> Thread [DestroyJavaVM] (Running).
> As a result, the NodeManager keeps running even though no services are
> started.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
