[ https://issues.apache.org/jira/browse/MAPREDUCE-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123859#comment-13123859 ]
Hudson commented on MAPREDUCE-2876: ----------------------------------- Integrated in Hadoop-Hdfs-trunk-Commit #1126 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1126/]) MAPREDUCE-2876. Use a different config for ContainerAllocationExpirer. Contributed by Anupam Seth. acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180767 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NMLivelinessMonitor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/AMLivelinessMonitor.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/ContainerAllocationExpirer.java > ContainerAllocationExpirer appears to use the incorrect configs > --------------------------------------------------------------- > > Key: MAPREDUCE-2876 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2876 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Robert Joseph Evans > Assignee: Anupam Seth > Priority: Critical > Fix For: 0.23.0 > > Attachments: MAPREDUCE-2876-branch-0_23.patch, > MAPREDUCE-2876-branch-0_23.patch > > > ContainerAllocationExpirer sets the expiration interval to be > RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL but uses > AMLIVELINESS_MONITORING_INTERVAL as the interval. This is very different > from what AMLivelinessMonitor does. > There should be two configs RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL > for the monitoring interval and RMConfig.CONTAINER_EXPIRY_INTERVAL for the > expiry. -- 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