hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-433) When RM is catching up with node updates then it should not expire acquired containers
Date Wed, 27 Feb 2013 23:07:13 GMT
Bikas Saha created YARN-433:
-------------------------------

             Summary: When RM is catching up with node updates then it should not expire acquired
containers
                 Key: YARN-433
                 URL: https://issues.apache.org/jira/browse/YARN-433
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Bikas Saha
            Assignee: Xuan Gong


RM expires containers that are not launched within some time of being allocated. The default
is 10mins. When an RM is not keeping up with node updates then it may not be aware of new
launched containers. If the expire thread fires for such containers then the RM can expire
them even though they may have launched.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message