Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 13 Sep 2012 12:56:09 +1100 (NCT)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <1243418259.72906.1347501369744.JavaMail.jiratomcat@arcas>
Subject: [jira] [Moved] (YARN-104) Add a yarn kill command
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli moved MAPREDUCE-3793 to YARN-104:
---------------------------------------------------------

          Component/s:     (was: mrv2)
                       client
     Target Version/s:   (was: 0.24.0)
    Affects Version/s:     (was: 0.23.1)
                           (was: 0.24.0)
                  Key: YARN-104  (was: MAPREDUCE-3793)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> Add a yarn kill command 
> ------------------------
>
>                 Key: YARN-104
>                 URL: https://issues.apache.org/jira/browse/YARN-104
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: client
>            Reporter: Robert Joseph Evans
>
> There currently is a mapreduce kill command to kill a single mapreduce job, but in order to better administer a grid it would be nice to be able to kill a misbehaving application no matter what AM it is running.

--
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