hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1646) Task Killing tests
Date Mon, 05 Apr 2010 20:52:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853536#action_12853536
] 

Konstantin Boudnik commented on MAPREDUCE-1646:
-----------------------------------------------

bq. I have checked your log file and the first test(testFailedTaskJobStatus ) failed due to
task has not been started for almost 1 min, so it got failed.And the other two tests are failing
due to error in configuration object. I am suspecting the failures might occurred due to environmental
issue.

- Shall the limit be raised slightly? Say 2 mins?
- 'Good citizen' test should be unrelated to environment as much as possible. If you can provide
some special settings in the test config - you should do so, If test requires a particular
environment to exist at the moment of a test execution and such env. setting doesn't exist
then the test in question should fail with proper and meaningful error message. E.g. a person
who runs tests shouldn't be guessing the required environment. 

> Task Killing tests
> ------------------
>
>                 Key: MAPREDUCE-1646
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1646
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: test
>            Reporter: Vinay Kumar Thota
>            Assignee: Vinay Kumar Thota
>         Attachments: TaskKilling_1646.patch, TaskKilling_1646.patch, TaskKilling_1646.patch,
TEST-org.apache.hadoop.mapred.TestTaskKilling.txt, TEST-org.apache.hadoop.mapred.TestTaskKilling.txt
>
>
> The following tasks covered in the test.
> 1. In a running job, kill a task and verify the job succeeds.
> 2. Setup a job with long running tasks that write some output to HDFS. When one of the
tasks is running, ensure that
> the output/_temporary/_attempt-id directory is created. Kill the task. After the task
is killed, make sure that the
> output/_temporary/_attempt-id directory is cleaned up.
> 3. Setup a job with long running tasks that write some output to HDFS. When one of the
tasks is running, ensure that
> the output/_temporary/_attempt-id directory is created. Fail the task by simulating the
map. After the task is failed,
> make sure that the output/_temporary/_attempt-id directory is cleaned up. The important
difference we are trying to
> check is btw kill and fail, there would a subtle difference.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message