From hadoop-dev-return-14259-apmail-lucene-hadoop-dev-archive=lucene.apache.org@lucene.apache.org Wed Jul 04 06:30:30 2007 Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 77511 invoked from network); 4 Jul 2007 06:30:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2007 06:30:28 -0000 Received: (qmail 65851 invoked by uid 500); 4 Jul 2007 06:30:31 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 65246 invoked by uid 500); 4 Jul 2007 06:30:28 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 65222 invoked by uid 99); 4 Jul 2007 06:30:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2007 23:30:28 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2007 23:30:25 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C89C47141F3 for ; Tue, 3 Jul 2007 23:30:04 -0700 (PDT) Message-ID: <32167761.1183530604818.JavaMail.jira@brutus> Date: Tue, 3 Jul 2007 23:30:04 -0700 (PDT) From: "Enis Soztutar (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-1351) Want to kill a particular task or attempt In-Reply-To: <2515095.1178917935311.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510079 ] Enis Soztutar commented on HADOOP-1351: --------------------------------------- Thanks Arun for the suggestion, > mark the task as FAILED (and not KILLED since you want this attempt to count against the job). Actually i think, we should label the task as KILLED, rather than FAILED, since killing is a task is quite an explicit action done by the user examining the system so she may prefer seeing the task as KILLED (Although in the similar case for killing jobs we do not have KILLED status for a job, so killed jobs appear as FAILED). Also, regarding our use cases, we do not want to "black label" the machine for killed task ({{machinesWhereFailed}}), that's why i have written {{taskKilled}} instead of using {{incompleteSubTask}}. I will look deeper into using {{TaskInProgress.shouldCloseForClosedJob }} and {{tasksReportedClosed}}. I bet having a generic DFA implementation will benefit us in this. > Want to kill a particular task or attempt > ----------------------------------------- > > Key: HADOOP-1351 > URL: https://issues.apache.org/jira/browse/HADOOP-1351 > Project: Hadoop > Issue Type: New Feature > Components: mapred > Affects Versions: 0.12.3 > Reporter: Owen O'Malley > Assignee: Enis Soztutar > Fix For: 0.14.0 > > Attachments: killTask_v1.0.1.patch > > > It would be convenient to be able to kill a particular task or attempt from the command line. It would look like: > bin/hadoop job -kill-task tip_0001_m_000000 > bin/hadoop job -kill-attempt task_0001_m_000000_0 > This would allow the user to tell the system to stop a particular task or attempt without having to restart a task tracker. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.