[
https://issues.apache.org/jira/browse/HADOOP-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671215#action_12671215
]
Ravi Gummadi commented on HADOOP-4191:
--------------------------------------
Discussed offline with Amar and came up with the following approach for testing
job history:
Run a job that will be succeeded and validate its history file content
(1) history file exists and in correct location
(2) Verify if the history file is parsable
(3) Validate the contents of history file
(a) validate job level key, values
(b) validate task level key, values
(c) validate attempt level key, values
(d) check if all the TaskAttempts, Tasks started are finished
Run jobs with for the given values of hadoop.job.history.user.location as
(1)null(default case), (2)"none", and (3)some dir like "/tmp".
Validate user history file location in each case.
Run jobs that will be (1) succeeded (2) failed (3) killed.
Validate job status read from history file in each case.
Thoughts ?
> Add a testcase for jobhistory
> -----------------------------
>
> Key: HADOOP-4191
> URL: https://issues.apache.org/jira/browse/HADOOP-4191
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred, test
> Reporter: Amar Kamat
> Assignee: Ravi Gummadi
>
> Changes in job history might break the history parser which in turn might
> break some features like jobtracker-recovery, history-viewer etc. There
> should be a testcase that catches these incompatible changes early and
> informs about the expected change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
