[
https://issues.apache.org/jira/browse/MAPREDUCE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102239#comment-13102239
]
Ravi Teja Ch N V commented on MAPREDUCE-2949:
---------------------------------------------
We have two problems with the ResourceLocalizationService initialization
1.Starting of the PublicLocalizer thread.
2.CacheCleanup timer is scheduled.
These two threads are blocking the JVM exit.
Ideally these are meant to be done when the service is started.
Hi Vinod,
Can we perform these tasks at the startup of the service rather than at
initialization.
| We should just make ResourceLocalizationService.LocalizerTracker itself a
service
I think LocalizerTracker should be under the ResourceLocalizationService as its
not generic enough, to be made a seperate service.I feel that moving the tasks
to the service startup may be a good thing.
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
> Attachments: Threaddump.txt
>
>
> 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
