Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4ABDADFC2 for ; Thu, 6 Dec 2012 15:32:31 +0000 (UTC) Received: (qmail 59180 invoked by uid 500); 6 Dec 2012 15:32:22 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 58977 invoked by uid 500); 6 Dec 2012 15:32:22 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 58961 invoked by uid 99); 6 Dec 2012 15:32:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:32:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2012 15:32:16 +0000 Received: by mail-ia0-f169.google.com with SMTP id r4so4706656iaj.28 for ; Thu, 06 Dec 2012 07:31:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=b0InbjkGQaEOv+nDuNwMoRhtE0fvdMnW6YNtxUCtaxA=; b=kBb5w8628rRzj+njCZ+oDLqrOMVRJD5fUJt3vm/N+iRmaxZk988mskir1HAeCkRDHP TwkOEqXRr8zcR2L72tXNJlFwZSvFzJNxwuXN+h3n+RYazRhN8oKzLROA9T/IE3aTfFKM gw4LpWzSMpX3y1o1JOLVIsYJj0cReHG+gQ/G2N4Tr1Slfy+EB4NBR1L+1kbDrdA0w3/f PakEMVcYUHlDPdP5Jie6cnJUN9GCDrQyUmcVXv8zf6iyhF1Kvx9Su2bSXxMgixp5k6A5 ZJz3RdSBZf+4ZBpo6sIGbgNIHYgljJbWCZL4gbu7VWrSKhQtFzUVO0bEihgpEdvX8Ko4 jGWw== Received: by 10.50.181.135 with SMTP id dw7mr1829762igc.40.1354807916479; Thu, 06 Dec 2012 07:31:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.6.129 with HTTP; Thu, 6 Dec 2012 07:31:36 -0800 (PST) In-Reply-To: <8455FB51-E685-463A-9628-F95E2150CF3C@guavus.com> References: <059401cdd379$093452e0$1b9cf8a0$@yahoo.com> <1354776326.401.YahooMailNeo@web160704.mail.bf1.yahoo.com> <05bc01cdd384$70d78a10$52869e30$@yahoo.com> <05ed01cdd394$41c51cf0$c54f56d0$@yahoo.com> <8455FB51-E685-463A-9628-F95E2150CF3C@guavus.com> From: Harsh J Date: Thu, 6 Dec 2012 21:01:36 +0530 Message-ID: Subject: Re: Query about Speculative Execution To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmi7/TNeQq2MxKhDtDhftN/tTFaoI7/kA9XomJUQTzxBVEsHaa+UqKu3eTaL8u6Odp4mDWF X-Virus-Checked: Checked by ClamAV on apache.org Given that Speculative Execution *is* the answer to such scenarios, I'd say the answer to your question without it, is *nothing*. If a task does not report status for over 10 minutes (default), it is killed and retried. If it does report status changes (such as counters, task status, etc.) but is slow due to environmental or other reasons, then the JobTracker, without speculative execution logic turned on, will assume it is normal. On Thu, Dec 6, 2012 at 8:27 PM, Ajay Srivastava wrote: > Hi, > > What is the behavior of jobTracker if speculative execution is off and a task on data node is running extremely slow? > Will the jobTracker simply wait till the slow running task finishes or it will try to heal the situation? Assuming that heartbeat from the node running slow task are regular. > > > > Regards, > Ajay Srivastava -- Harsh J