[
https://issues.apache.org/jira/browse/HADOOP-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4189:
-------------------------------
Attachment: HADOOP-4189-v1.patch
Attaching a updated patch that solves the issue of stale job history analysis.
Pre HADOOP-3245, missing job state meant that the job is running. HADOOP-3245
introduces the RUNNING state for jobs which indicates that the job meta-info is
available in the history. {{loadhistory.jsp}} cached the analysis results and
refreshed only if the job status was missing (which meant that the job is
running). Fixed that to explicitly test the job runstate as RUNNING. Tested the
patch with and without restarts. Also checked if the history analysis works
after the job is complete. I apologize for not testing this before, my bad.
> HADOOP-3245 is incomplete
> -------------------------
>
> Key: HADOOP-4189
> URL: https://issues.apache.org/jira/browse/HADOOP-4189
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Attachments: HADOOP-4189-v1.patch, HADOOP-4189.patch
>
>
> There are 2 issues with HADOOP-3245
> - The default block size for the history files in hadoop-default.conf is set
> to 0. This file will be empty throughout. It should be made null.
> - Same goes for the buffer size.
> - InterTrackerProtocol version needs to be bumped.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
