hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4157) ResourceManager should not kill apps that are well behaved
Date Wed, 25 Apr 2012 13:48:21 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261646#comment-13261646
] 

Jason Lowe commented on MAPREDUCE-4157:
---------------------------------------

Those properties are unrelated to this scenario.  They are properties for the nodemanager
to control how long to wait for a process to generate its pid file and how long to wait after
sending SIGTERM before we send SIGKILL, respectively.  In this case, we're not waiting for
the process to generate a pid file nor waiting for it to die after sending SIGTERM.  We're
waiting for the process to exit normally on its own accord.  If it doesn't exit normally,
then the SIGTERM/SIGKILL approach and sleep-delay-before-sigkill would be relevant.

                
> ResourceManager should not kill apps that are well behaved
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4157
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4157
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 2.0.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: MAPREDUCE-4157.patch
>
>
> Currently when the ApplicationMaster unregisters with the ResourceManager, the RM kills
(via the NMs) all the active containers for an application.  This introduces a race where
the AM may be trying to clean up and may not finish before it is killed.  The RM should give
the AM a chance to exit cleanly on its own rather than always race with a pending kill on
shutdown.

--
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