Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-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 5BAC3CD32 for ; Wed, 18 Jul 2012 18:21:38 +0000 (UTC) Received: (qmail 47332 invoked by uid 500); 18 Jul 2012 18:21:37 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 47303 invoked by uid 500); 18 Jul 2012 18:21:37 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 47170 invoked by uid 500); 18 Jul 2012 18:21:37 -0000 Delivered-To: apmail-incubator-hama-dev@incubator.apache.org Received: (qmail 47129 invoked by uid 99); 18 Jul 2012 18:21:37 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2012 18:21:37 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id B0D9014286C for ; Wed, 18 Jul 2012 18:21:36 +0000 (UTC) Date: Wed, 18 Jul 2012 18:21:36 +0000 (UTC) From: "Thomas Jungblut (JIRA)" To: hama-dev@incubator.apache.org Message-ID: <1963347055.70423.1342635696730.JavaMail.jiratomcat@issues-vm> In-Reply-To: <2034702346.70323.1342635214809.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HAMA-610) Provision to define the task allocation strategy as a feature of job. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HAMA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417340#comment-13417340 ] Thomas Jungblut commented on HAMA-610: -------------------------------------- Cool. Just a question, otherwise I'm +1 for this patch. Why is TaskAllocationStrategy not an interface, same with BSPResource? > Provision to define the task allocation strategy as a feature of job. > --------------------------------------------------------------------- > > Key: HAMA-610 > URL: https://issues.apache.org/jira/browse/HAMA-610 > Project: Hama > Issue Type: New Feature > Components: bsp core > Affects Versions: 0.6.0 > Reporter: Suraj Menon > Assignee: Suraj Menon > Fix For: 0.6.0 > > Attachments: HAMA-610.patch > > > With this feature, BSP Job Submission could define a task-allocation strategy per job depending on the nature of the job. This allocation strategy should be usable by the scheduler to find the grooms to allocate tasks to. The allocation strategy should get a list of resource objects and provide a list of grooms such that we could schedule the tasks on grooms that has the specified resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira