hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2876) ContainerAllocationExpirer appears to use the incorrect configs
Date Fri, 07 Oct 2011 21:38:30 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun C Murthy updated MAPREDUCE-2876:
-------------------------------------

     Target Version/s: 0.23.0  (was: 0.24.0, 0.23.0)
    Affects Version/s:     (was: 0.24.0)
               Status: Open  (was: Patch Available)

Cancelling patch while Mahadev's comments are addressed.
                
> 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
>
>
> 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

        

Mime
View raw message