[
https://issues.apache.org/jira/browse/MAPREDUCE-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568891#comment-14568891
]
Steve Loughran commented on MAPREDUCE-3820:
-------------------------------------------
Is this still an issue? The container exit codes do contain values for limits
exceeded, preempted, node failed, etc. It'll be up to MRv2 to handle them
> Improve logging when containers run beyond memory limits
> --------------------------------------------------------
>
> Key: MAPREDUCE-3820
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3820
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Ramya Sunil
> Priority: Minor
>
> When containers run beyond memory limits, they are killed without logging any
> useful message. Diagnostics message reads "Task attemptID failed 0 times" and
> the console output reads "INFO mapreduce.Job: Job jobID failed with state
> KILLED due to:" which are both not useful. This message has to be improved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
