Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.7.3
-
None
-
None
Description
When AM crashes, Yarn would launch a new AM instance and recover all its scheduled tasks. However mapper tasks's committed output files are not recovered when the number of reducers > 0. In my application which output files from mapper and make use of reducer to collect statistics not able to fully recover from the AM crash, and resulting in data from the previous completed mapper tasks get lost in the final output dir.