Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <4630122.235251278486830019.JavaMail.jira@thor>
Date: Wed, 7 Jul 2010 03:13:50 -0400 (EDT)
From: "Iyappan Srinivasan (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1730) Automate test scenario for
 successful/killed jobs' memory is properly removed from jobtracker after
 these jobs retire.
In-Reply-To: <27843972.28021272354332705.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Iyappan Srinivasan updated MAPREDUCE-1730:
------------------------------------------

    Attachment: TestRetiredJobs-ydist-security-patch.txt

Removed Thread statements and introduced UtilsForTests.waitFor method.

- Also introduced a variable, picked from mapred.jobtracker.retirejob.check, which will handle waiting times better. Tested it too. Since this code is already checked in, the diff patch is attached. 

For trunk, patch will have the full testcase.

> Automate test scenario for successful/killed jobs' memory is properly removed from jobtracker after these jobs retire.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1730
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1730
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>    Affects Versions: 0.22.0
>            Reporter: Iyappan Srinivasan
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1730.patch, MAPREDUCE-1730.patch, TestJobRetired.patch, TestJobRetired.patch, TestRetiredJobs-ydist-security-patch.txt, TestRetiredJobs-ydist-security-patch.txt, TestRetiredJobs.patch
>
>
> Automate using herriot framework,  test scenario for successful/killed jobs' memory is properly removed from jobtracker after these jobs retire.
> This should test when successful and failed jobs are retired,  their jobInProgress object are removed properly.

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