Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 356CB10B02 for ; Tue, 2 Jul 2013 21:03:23 +0000 (UTC) Received: (qmail 20564 invoked by uid 500); 2 Jul 2013 21:03:20 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 20512 invoked by uid 500); 2 Jul 2013 21:03:20 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 20407 invoked by uid 99); 2 Jul 2013 21:03:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 21:03:20 +0000 Date: Tue, 2 Jul 2013 21:03:20 +0000 (UTC) From: "Cindy Li (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MAPREDUCE-5370) Rolling Restart Tasktrackers from JobTracker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Cindy Li created MAPREDUCE-5370: ----------------------------------- Summary: Rolling Restart Tasktrackers from JobTracker Key: MAPREDUCE-5370 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5370 Project: Hadoop Map/Reduce Issue Type: Task Reporter: Cindy Li Priority: Minor For near real-time jobs running on hadoop, we want to minimize impact on them when rolling restarting tasktrackers. The idea here is to restart tasktrackers from jobtracker and selectively choose task trackers according to tasks' status on them to do rolling restart, such that the impact on total job running time is minimum. -- 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