Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <20674157.184301288652186472.JavaMail.jira@thor>
Date: Mon, 1 Nov 2010 18:56:26 -0400 (EDT)
From: "Tom White (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-2051) Contribute a fair scheduler
 preemption system test
In-Reply-To: <32176260.3001283471254437.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-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated MAPREDUCE-2051:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I've just committed this. Thanks Todd!

> Contribute a fair scheduler preemption system test
> --------------------------------------------------
>
>                 Key: MAPREDUCE-2051
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2051
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: contrib/fair-share
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.22.0
>
>         Attachments: mapreduce-2051.txt
>
>
> We've seen a number of bugs in the fair share scheduler not caught by its unit tests, which are heavily mock-based. This JIRA is to add an integration/system/stress test for the fairshare scheduler. This test can help identify races and deadlocks, and when run within the jcarder framework has identified several potential deadlocks for us that aren't turned up running small scale testing.

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