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 19B01106D0 for ; Thu, 21 Nov 2013 10:59:54 +0000 (UTC) Received: (qmail 77534 invoked by uid 500); 21 Nov 2013 10:59:45 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 77264 invoked by uid 500); 21 Nov 2013 10:59:45 -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 77257 invoked by uid 99); 21 Nov 2013 10:59:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 10:59:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of write2kishore@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Nov 2013 10:59:38 +0000 Received: by mail-qa0-f51.google.com with SMTP id o15so3713041qap.3 for ; Thu, 21 Nov 2013 02:59:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yAvFmIsD20g19eWNFXvl3O1FgSrPw5jqJtwwtL4GtL4=; b=t7xOmzx6UXUJ/vfvmtNf+0dLQrdE4DMPj8bZ24WlWE1qL3Dugtpij2LA1UV9ndy7FI GW65NDL9HupBT/2NcTD8/Z2n8G4NxBWOSOKsbOA3afcTlInlRDWTXeX6C5QlI9vsGjjl r3fYZ+krWHg7phi4KpWun1JDp+Zx0sTIIyp3FXDBXM+K6tCeqUtC9/V7GRPu6ZEjlgM4 S0RlM01POuzOtGHLupx0bZa/nfYcgBjH4NGdAXqN/YIto0N6eE8YlwuZTYQASRZaYfuF 5EicH8X8HZuFVCQ5edwnO0YacjkIrQ1TytsoRnvlEEpmcKDeTxcvHy1zoV/Z4VCx+PiX P/2A== MIME-Version: 1.0 X-Received: by 10.49.109.97 with SMTP id hr1mr9707884qeb.59.1385031557632; Thu, 21 Nov 2013 02:59:17 -0800 (PST) Received: by 10.96.154.40 with HTTP; Thu, 21 Nov 2013 02:59:17 -0800 (PST) In-Reply-To: <2075D494-C37A-4FC6-A509-356D05C11A22@hortonworks.com> References: <2075D494-C37A-4FC6-A509-356D05C11A22@hortonworks.com> Date: Thu, 21 Nov 2013 16:29:17 +0530 Message-ID: Subject: Re: Time taken for starting AMRMClientAsync From: Krishna Kishore Bonagiri To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bea31a6fed77404ebadc934 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bea31a6fed77404ebadc934 Content-Type: text/plain; charset=ISO-8859-1 Vinod, Do you expect managed AMs also not take as much time as a second? Or as Alejandro was saying, only unmanaged AMs? I think I am using managed AMs. If managed AMs also are not expected to take that much time, I shall raise a ticket. Thanks, Kishore On Mon, Nov 18, 2013 at 12:46 AM, Vinod Kumar Vavilapalli < vinodkv@hortonworks.com> wrote: > It is just creating a connection to RM and shouldn't take that long. Can > you please file a ticket so that we can look at it? > > JVM class loading overhead is one possibility but 1 sec is a bit too much. > > Thanks, > +Vinod > > On Oct 21, 2013, at 7:16 AM, Krishna Kishore Bonagiri wrote: > > Hi, > I am seeing the following call to start() on AMRMClientAsync taking from > 0.9 to 1 second. Why does it take that long? Is there a way to reduce it, I > mean does it depend on any of the interval parameters or so in > configuration files? I have tried reducing the value of the first argument > below from 1000 to 100 seconds also, but that doesn't help. > > AMRMClientAsync.CallbackHandler allocListener = new > RMCallbackHandler(); > amRMClient = AMRMClientAsync.createAMRMClientAsync(1000, > allocListener); > amRMClient.init(conf); > amRMClient.start(); > > > Thanks, > Kishore > > > > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. --047d7bea31a6fed77404ebadc934 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Vinod,

=A0 Do you expect managed AMs also not= take as much time as a second? Or as Alejandro was saying, only unmanaged = AMs?

=A0 I think I am using managed AMs. If ma= naged AMs also are not expected to take that much time, I shall raise a tic= ket.

Thanks,
Kishore


On Mon, Nov 18, 2013 at= 12:46 AM, Vinod Kumar Vavilapalli <vinodkv@hortonworks.com><= /span> wrote:
It is ju= st creating a connection to RM and shouldn't take that long. Can you pl= ease file a ticket so that we can look at it?

JVM class loading overhead is one possibility but 1 sec is a= bit too much.

Thanks,
+Vinod

On Oct 21, 2013, at 7:16 AM, Krishna Kishore Bonagiri wrote:<= /div>
Hi,
=A0 I am seeing= the following call to start() on AMRMClientAsync taking from 0.9 to 1 seco= nd. Why does it take that long? Is there a way to reduce it, I mean does it= depend on any of the interval parameters or so in configuration files? I h= ave tried reducing the value of the first argument below from 1000 to 100 s= econds also, but that doesn't help.

=A0 =A0 AMRMClientAsync.CallbackHandler allocListe= ner =3D new RMCallbackHandler();
=A0 =A0 amRMClient =3D AMRMClien= tAsync.createAMRMClientAsync(1000, allocListener);
=A0 =A0 amRMCl= ient.init(conf);
=A0 =A0 amRMClient.start();


<= div>Thanks,
Kishore



CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u.
--047d7bea31a6fed77404ebadc934--