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 < vino...@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.
