Return-Path: 
 <common-dev-return-75159-apmail-hadoop-common-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org
Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5CFB41F22
	for <apmail-hadoop-common-dev-archive@www.apache.org>;
 Tue, 26 Apr 2011 16:58:58 +0000 (UTC)
Received: (qmail 34650 invoked by uid 500); 26 Apr 2011 16:58:53 -0000
Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org
Received: (qmail 34431 invoked by uid 500); 26 Apr 2011 16:58:53 -0000
Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-dev@hadoop.apache.org>
List-Id: <common-dev.hadoop.apache.org>
Reply-To: common-dev@hadoop.apache.org
Delivered-To: mailing list common-dev@hadoop.apache.org
Received: (qmail 34417 invoked by uid 99); 26 Apr 2011 16:58:53 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2011 16:58:53 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of airbots@gmail.com designates
 74.125.82.48 as permitted sender)
Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2011 16:58:46 +0000
Received: by wwi18 with SMTP id 18so1002145wwi.29
        for <multiple recipients>; Tue, 26 Apr 2011 09:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=F6GfKxLjsvjwbufhaYdT3Mhu2brTOVclyCRbO4apGHY=;
        b=dBTHSUZr2B0VW7ViTaWRNMt2H6z9AnRrdWF1Y11lqnrO3b5Ykfq4bmNcOUXC1Di/FK
         7KtrHoh4BLSF/F2mR/FxVTu16hLytC1UlKEySZ31vvYzPQPq/tpswxVqLGnpEZi760Fd
         f0ZE3H9AzIR3Ho8zMyjzdYpsUzkw4PAsslfuw=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=W+EldekTHeFfSrLau0Fvq0O652tX0ZSSACuJqLcxqIehjlK7f/xn9PKRPrWaaSUmHk
         huMElP7tiqex9iPIw17Rtti2TJisVi+K1RwiKojWOpEZ7d8VJkTr2IPkpHVELRkrN7Xi
         QxxKCIMDZEzzom1OyyJTWN/UFcEM/VnN5mTFM=
MIME-Version: 1.0
Received: by 10.216.16.32 with SMTP id g32mr4786376weg.0.1303837105805; Tue,
 26 Apr 2011 09:58:25 -0700 (PDT)
Received: by 10.216.0.132 with HTTP; Tue, 26 Apr 2011 09:58:25 -0700 (PDT)
Date: Tue, 26 Apr 2011 11:58:25 -0500
Message-ID: <BANLkTi=rOemiABcWk7BpW5_++-0cp_2dMA@mail.gmail.com>
Subject: Apply HADOOP-4667 to branch-0.20
From: He Chen <airbots@gmail.com>
To: common-dev@hadoop.apache.org, common-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0015175932e0895a7904a1d53bd0
X-Virus-Checked: Checked by ClamAV on apache.org

--0015175932e0895a7904a1d53bd0
Content-Type: text/plain; charset=ISO-8859-1

Hey everyone

I tried to apply HADOOP-4667 patch to branch-0.20, but always failed.
Because my cluster is based on branch-0.20, however, I want to test the
delay scheduling method performance. I do not want to re-format the HDFS.

Then I tried to apply HADOOP-4667 to branch-0.20. Anyone did this before or
any suggestion?   Thank you in advance.

Best wishes!

Chen

--0015175932e0895a7904a1d53bd0--