Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 41937 invoked from network); 28 Apr 2009 03:28:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Apr 2009 03:28:56 -0000 Received: (qmail 52009 invoked by uid 500); 28 Apr 2009 03:28:55 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 51942 invoked by uid 500); 28 Apr 2009 03:28:55 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 51932 invoked by uid 99); 28 Apr 2009 03:28:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2009 03:28:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2009 03:28:53 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 736F4234C003 for ; Mon, 27 Apr 2009 20:28:32 -0700 (PDT) Message-ID: <2002682642.1240889312345.JavaMail.jira@brutus> Date: Mon, 27 Apr 2009 20:28:32 -0700 (PDT) From: "eric baldeschwieler (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-5643) Ability to blacklist tasktracker In-Reply-To: <1226222670.1239216312962.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703482#action_12703482 ] eric baldeschwieler commented on HADOOP-5643: --------------------------------------------- Do we have a good security story for actions taken through the web UI? Absent that, I'd suggest we don't enable this there. Being able to modify the excludes file and hup the server is probably good enough for an operator. > Ability to blacklist tasktracker > -------------------------------- > > Key: HADOOP-5643 > URL: https://issues.apache.org/jira/browse/HADOOP-5643 > Project: Hadoop Core > Issue Type: New Feature > Affects Versions: 0.20.0 > Reporter: Rajiv Chittajallu > Assignee: Amar Kamat > > Its not always possible to shutdown the tasktracker to stop scheduling tasks on the node. (eg you can't login to the node but the TT is up). > This can be via > * mapred.exclude and should be refreshed with out restarting the tasktracker > * hadoop job -fail-tracker -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.