[
https://issues.apache.org/jira/browse/MAPREDUCE-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285535#comment-13285535
]
Nishan Shetty commented on MAPREDUCE-4292:
------------------------------------------
bq. What exactly was the failed map's cause? Did the job not fail after 4x map
fails? (Note: Reducers may fail and retrigger maps if they can't get its
outputs in good time.)
I was testing a scenario where some maps fail always. Job did not fail after
failing 4 attempts. Reducers were waiting for the map outputs.
bq. Logs of the MR AM would be good to have.
I have attached the am log.
> Job is hanging forever when some maps are failing always
> --------------------------------------------------------
>
> Key: MAPREDUCE-4292
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4292
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Nishan Shetty
> Priority: Critical
> Attachments: syslog.dat
>
>
> Set property "mapred.reduce.tasks" to some value greater than zero
> I have a job in which some maps are failing always.
> Observations:
> 1.Map phase is completing with 100%(with succeeded and failed maps).
> 2.Reduce phase is not progressing further after 32%.
> 3.After map phase is completed job is hanging forever.
> Expected that job should be failed after waiting for some time.
--
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