We are seeing a case where a job runs but the AM is running out of memory in the first 3 attempts. The job eventually finishes on the 4th attempt. When you go to the job history UI for that job, it only shows the last attempt. This is bad since we want to see why the first 3 attempts failed.
The RM web ui shows all 4 attempts.
Also I tested this locally by running "kill" on the app master and in that case the history server UI does show all attempts.