Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1044220713.1253682196019.JavaMail.jira@brutus>
Date: Tue, 22 Sep 2009 22:03:16 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-760) TestNodeRefresh might not work as
 expected
In-Reply-To: <930888091.1247568854888.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amar Kamat updated MAPREDUCE-760:
---------------------------------

    Release Note: TestNodeRefresh waits for the newly added tracker to join before starting the testing.

> TestNodeRefresh might not work as expected
> ------------------------------------------
>
>                 Key: MAPREDUCE-760
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-760
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>             Fix For: 0.21.0
>
>         Attachments: MAPREDUCE-760-v1.0.patch
>
>
> MAPREDUCE-677 fixed one part of the problem. It is possible that the tasktracker might not have joined the jobtracker and hence the asserts might fail.

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