hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4729) job history UI not showing all job attempts
Date Thu, 01 Nov 2012 21:06:13 GMT

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

Vinod Kumar Vavilapalli updated MAPREDUCE-4729:
-----------------------------------------------

    Attachment: MAPREDUCE-4729-20121101.txt

Thanks for testing this Jason. And for the comments too.

bq. We will want to flush/sync the job history file after writing the AMInfos to help guard
against unclean teardowns losing prior AM attempts in the history.
Wanted to this, but ran into couple more not so critical bugs - setupEventWriter() is getting
called for all AMStarted events! Let's fix both in a separate ticket.

Fixed the other issues. Good catch on the AttemptId part.
                
> job history UI not showing all job attempts
> -------------------------------------------
>
>                 Key: MAPREDUCE-4729
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4729
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: MAPREDUCE-4729-20121031.txt, MAPREDUCE-4729-20121101.txt
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message