hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2876) ContainerAllocationExpirer appears to use the incorrect configs
Date Fri, 26 Aug 2011 15:30:29 GMT

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

Mahadev konar commented on MAPREDUCE-2876:

  I think we can leave the setMonitor API. I was saying something along the lines of:

When creating NMLivenessMonitor:




So in case someone wants to use Livenessmonitor with almost the same interval as expiry can
use it that way. Seems reasonable?

> 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: Robert Joseph Evans
>             Fix For: 0.23.0
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message