From yarn-dev-return-982-apmail-hadoop-yarn-dev-archive=hadoop.apache.org@hadoop.apache.org Mon Feb 25 09:18:16 2013 Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7DE0FEBC5 for ; Mon, 25 Feb 2013 09:18:16 +0000 (UTC) Received: (qmail 50048 invoked by uid 500); 25 Feb 2013 09:18:15 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 49854 invoked by uid 500); 25 Feb 2013 09:18:14 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 49792 invoked by uid 99); 25 Feb 2013 09:18:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 09:18:13 +0000 Date: Mon, 25 Feb 2013 09:18:13 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-424) Allow resource requests to provide hints to the scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sandy Ryza created YARN-424: ------------------------------- Summary: Allow resource requests to provide hints to the scheduler Key: YARN-424 URL: https://issues.apache.org/jira/browse/YARN-424 Project: Hadoop YARN Issue Type: Improvement Components: api, applications, scheduler Affects Versions: 2.0.3-alpha Reporter: Sandy Ryza Assignee: Sandy Ryza As initially discussed on YARN-392, it would be helpful for the allocate protocol to be able to include hints to the scheduler. Examples hints could include deadlines (containers needed by a certain time) or gangs (resources that should be scheduled at the same time or not at all). To avoid placing complex scheduling expectations on the RM, the restrictions on hints would be: * Any scheduler may ignore any subset of hints. That is, applications must be written to handle resource requests as if their hints don't exist. * Must be bounded in length - perhaps no larger than 16 bytes or 100 characters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira