Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 5 Mar 2011 07:45:46 +0000 (UTC)
From: "Lianhui Wang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1106148930.735.1299311146133.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (MAPREDUCE-279) Map-Reduce 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MAPREDUCE-279?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
3002947#comment-13002947 ]=20

Lianhui Wang commented on MAPREDUCE-279:
----------------------------------------

i think that the MR2.0 may resolve the thing:
JT doesnot monitor the status of the every job and tasks,because many TT mu=
st RPC to the one JT every few seconds.
and many clients get the job's status through rpc the one JT every few seco=
nds.
so the majority nodes of the cluster connect to the JT discontinuously,that=
 lead to degrade the performance of the JT.especially the number of cluster=
 increase,example 10K.
like hdfs's Federation Branch=EF=BC=8C the MR project must create a new bra=
nch for the 2.0.=20


> Map-Reduce 2.0
> --------------
>
>                 Key: MAPREDUCE-279
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-279
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker, tasktracker
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 0.23.0
>
>
> Re-factor MapReduce into a generic resource scheduler and a per-job, user=
-defined component that manages the application execution.=20

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira