Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7B00BC63D for ; Thu, 19 Jul 2012 03:36:36 +0000 (UTC) Received: (qmail 1817 invoked by uid 500); 19 Jul 2012 03:36:36 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 1676 invoked by uid 500); 19 Jul 2012 03:36:36 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 1630 invoked by uid 99); 19 Jul 2012 03:36:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 03:36:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 0BB2F142865 for ; Thu, 19 Jul 2012 03:36:35 +0000 (UTC) Date: Thu, 19 Jul 2012 03:36:35 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <782368784.74180.1342668995049.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (MAPREDUCE-4309) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4309?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 13418031#comment-13418031 ]=20 Tsz Wo (Nicholas), SZE commented on MAPREDUCE-4309: --------------------------------------------------- Abstract Factory sounds good. For the enum problem, let's use enum for the moment and change it to interf= aces later. (Sorry that I was not able to response earlier.) =20 > Make locatlity in YARN's container assignment and task scheduling pluggab= le for other deployment topology > -------------------------------------------------------------------------= -------------------------------- > > Key: MAPREDUCE-4309 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4309 > Project: Hadoop Map/Reduce > Issue Type: Bug > Affects Versions: 1.0.0, 2.0.0-alpha > Reporter: Junping Du > Assignee: Junping Du > Attachments: HADOOP-8474-ContainerAssignmentTaskScheduling-plugga= ble.patch, MAPREDUCE-4309-v2.patch, MAPREDUCE-4309-v3.patch, MAPREDUCE-4309= -v4.patch, MAPREDUCE-4309-v5.patch, MAPREDUCE-4309.patch > > > There are several classes in YARN=E2=80=99s container assignment and task= scheduling algorithms that relate to data locality which were updated to g= ive preference to running a container on other locality besides node-local = and rack-local (like nodegroup-local). This propose to make these data stru= cture/algorithms pluggable, like: SchedulerNode, RMNodeImpl, etc. The inner= class ScheduledRequests was made a package level class to it would be easi= er to create a subclass, ScheduledRequestsWithNodeGroup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira