Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC93210D6A for ; Tue, 23 Jul 2013 03:16:36 +0000 (UTC) Received: (qmail 68463 invoked by uid 500); 23 Jul 2013 03:16:32 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 68348 invoked by uid 500); 23 Jul 2013 03:16:31 -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 68341 invoked by uid 99); 23 Jul 2013 03:16:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 03:16:31 +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 (nike.apache.org: domain of harsh@cloudera.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 03:16:26 +0000 Received: by mail-ie0-f170.google.com with SMTP id e11so17662423iej.29 for ; Mon, 22 Jul 2013 20:16:05 -0700 (PDT) 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=jRzmRZWHJEkW7FMZbO4rcOjjbYQLF7MpwATqrw/cb1M=; b=Q40n5bjSoRAQmziF9Zm0hjIp4kfAiFYajQ8+fAG/qSmpcVkF34oJnr7qWXW0gkPQQI zrqCv+gEHtDJNxXI5CVYCOmrKURbImTmotOsAkVt8yZFgeDn0RlrXWsaN9R0QA2GGUNi ljpotGVWTS/sBnjYs3dsYCHnNr4/2kBeVODZnEdJr136+gu925a+IaGh/TwPoLHRmidJ IJUsZMKFKVGbi46fLSlc1PpD9tgPw7kajCrT2qGzvwfNEhXDYSXaP+UZ33zN5iYEDjhY sHHAEpPpw3OXLluu1JTJZ+1aL1V2Mq7mqFFds8mNr3ZzwgcOY7vkYncS3bFhBI4l2pQ5 d39g== X-Received: by 10.43.139.133 with SMTP id iw5mr19052130icc.0.1374549364943; Mon, 22 Jul 2013 20:16:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.87.164 with HTTP; Mon, 22 Jul 2013 20:15:44 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Tue, 23 Jul 2013 08:45:44 +0530 Message-ID: Subject: Re: setting mapred.task.timeout programmatically from client To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkjjjUcIBpPzqNnrSlaKuRHBo4tEOw+GdvOLdP/bKhu9vF4Q/W66XzmhJPm3Ai3z8dSv0U0 X-Virus-Checked: Checked by ClamAV on apache.org Yes, you can set it into your Job configuration object in code. If your driver uses the Tool framework, then you can also pass a -Dmapred.task.timeout=value CLI argument when invoking your program. On Tue, Jul 23, 2013 at 4:24 AM, Eugene Koifman wrote: > Hello, > is there a way to set mapred.task.timeout programmatically from client? > > Thank you -- Harsh J