Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 43625 invoked from network); 2 Jan 2011 23:58:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Jan 2011 23:58:32 -0000 Received: (qmail 62870 invoked by uid 500); 2 Jan 2011 23:58:30 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 62801 invoked by uid 500); 2 Jan 2011 23:58:30 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 62793 invoked by uid 99); 2 Jan 2011 23:58:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jan 2011 23:58:30 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.191.69.19] (HELO web30002.mail.mud.yahoo.com) (209.191.69.19) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 02 Jan 2011 23:58:21 +0000 Received: (qmail 55938 invoked by uid 60001); 2 Jan 2011 23:57:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1294012679; bh=abh+Q1mY77HcUDS1l4jP+gK2XewzztTzG3jOGTm3NnE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=BrM10ZpNvP+TihxrE7qYM0AbKh5h32rSJ/1QfBin+kf4NUWtJggYCNawYnP73lV5uCNvrMAjeMySv2nb0ReJwWytjgLFXHpARz7fqMmVx8gK/ys2mOi2NOEfIvcBTzVTZX1ZYREV6obVn+q4zfL1D3fGQH4eZ49HlqhYHXAwQc4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=NfuZ+EGX0TFKtmsCxPQkmMpaRjBYVmCofa6RxeaiHSvITQWrYZ/CguaVoDutzIma+RP7u33W/tI7PAzgUnbS79s9TZ16cEhkR5r8L4QREyMVmwIdn2o8wW4r28AHlCqz4fNYB9Jp9ukUEscQYqzyKp8nAgpxABQSq8uNSt3T/aQ=; Message-ID: <761671.53492.qm@web30002.mail.mud.yahoo.com> X-YMail-OSG: sG8DDz4VM1mnlw.yhwh6gem27NFWXkdeaitviXX6CN.f2zI fzsKygQ6obRkgrKQmyHtVxZv898zRcs0yd7xtEI1qRBZXprSMWm7LYFMGSvY tfn4Cy162iEO26td6weAmdeJkP5_xZRU51j.jDIAKrPZaPbz47X1FVdsoJ59 A7Foj0ZzGzqw17kKwuJTapjknEklEsFMgZeqsGx6lLaWgb582aDpdgWaEybn CgnUOmXnLnzV2HbnIXZvTNIOjAyxTS3syJWP5yGeMTKLUwJOZ0QNZMSCo6LR frWTxu8OII17PgbIU3Q3dnb.KDU6PntdWCYgP2WpoLSL1OlbCDZtxqc2NlBS idF0xD6gZNYjldMeW84n4VD5D1bTwpnMG0LM3fteNxWB7JNSUHTqRDcvkBaa e8Gj8qLiMOIGP Received: from [76.126.156.12] by web30002.mail.mud.yahoo.com via HTTP; Sun, 02 Jan 2011 15:57:59 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259 Date: Sun, 2 Jan 2011 15:57:59 -0800 (PST) From: whorl1quote-re@yahoo.com Reply-To: whorl1quote-re@yahoo.com Subject: fair scheduler on memory usage To: common-user@hadoop.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-527767637-1294012679=:53492" X-Virus-Checked: Checked by ClamAV on apache.org --0-527767637-1294012679=:53492 Content-Type: text/plain; charset=us-ascii Can fair scheduler set an upper limit on a job's memory consumption? How do I use fair/capacity scheduler to make sure a long running (memory drain) job won't impact the service level of other higher priority jobs? --0-527767637-1294012679=:53492--