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] [Updated] (MAPREDUCE-5825) Provide diagnostics for reducers killed during ramp down
Date Thu, 10 Apr 2014 22:10:24 GMT

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

Jason Lowe updated MAPREDUCE-5825:
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.0
                   3.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks, Gera!  I committed this to trunk and branch-2.

> Provide diagnostics for reducers killed during ramp down
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-5825
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5825
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: MAPREDUCE-5825.v01.patch
>
>
> Since we operate many queues pretty much at their capacity it some times happens that
a failed mapper causes a reducer ramp down. However, the user can only see "Container killed
by the ApplicationMaster" as a diagnostic message for the task attempt, and have to dig through
the AM log in order to piece things together.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message