Re: Time taken for starting AMRMClientAsync

2013-11-17 Thread Krishna Kishore Bonagiri
Hi Alejandro,

  Can you please see if you can answer my question above? I would like to
reduce the time taken by the above calls made by my Application Master, the
way you do.

Thanks,
Kishore


On Tue, Oct 22, 2013 at 3:09 PM, Krishna Kishore Bonagiri 
write2kish...@gmail.com wrote:

 Hi Alejandro,

   I submit all my applications from a single Client, but all of my
 application masters are taking almost the same amount of time for finishing
 the above calls. Do you reuse ApplicationMaster instances or do some other
 thing for saving this time? Otherwise I felt the fresh application
 connecting to the resource manager would take the same amount of time
 although I don't know why should it take that much?

 Thanks,
 Kishore


 On Mon, Oct 21, 2013 at 9:23 PM, Alejandro Abdelnur t...@cloudera.comwrote:

 Hi Krishna,

 Those 900ms seems consistent with the numbers we  found while doing some
 benchmarks in the context of Llama:

 http://cloudera.github.io/llama/

 We found that the first application master created from a client process
 takes around 900 ms to be ready to submit resource requests. Subsequent
 application masters created from the same client process take a mean of 20
 ms. The application master submission throughput (discarding the first
 submission) tops at approximately 100 application masters per second.

 I believe there is room for improvement there.

 Cheers


 On Mon, Oct 21, 2013 at 7:16 AM, Krishna Kishore Bonagiri 
 write2kish...@gmail.com 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




 --
 Alejandro





unsubscribe

2013-11-17 Thread Levin ding
pls unsubscribe me, thanks.


Did anyone work with Hbase mapreduce with multiple table as input ?

2013-11-17 Thread samir das mohapatra
Dear hadoop/hbase developer

Did  Anyone work  with Hbase mapreduce with multiple table as input ?
   Any url-link or example  will help me alot.

  Thanks in advance.

Thanks,
samir.


Re: Did anyone work with Hbase mapreduce with multiple table as input ?

2013-11-17 Thread Ted Yu
Take a look at HBASE-3996

Cheers

On Nov 17, 2013, at 5:35 AM, samir das mohapatra samir.help...@gmail.com 
wrote:

 Dear hadoop/hbase developer

 Did  Anyone work  with Hbase mapreduce with multiple table as input ?
Any url-link or example  will help me alot.
 
   Thanks in advance.
 
 Thanks,
 samir.


Re: Time taken for starting AMRMClientAsync

2013-11-17 Thread Vinod Kumar Vavilapalli
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.