Re: Stats to look out for while running mapreduce jobs with HBase

2010-11-12 Thread Oleg Ruchovets
It is interesting point I am entering to hbase using m/r 1) map phase consumes 100% cpu 2) reducer phase (hbase insertions) consumes ~ 15% As I understand there are a lot of improvement could done here Can some recommend me what is the monitoring tool that is good to monitor map/reduce jobs.

Re: Stats to look out for while running mapreduce jobs with HBase

2010-11-12 Thread Hari Sreekumar
The current job is a bulk insert job and yes, I have some orange sections (cpu-wio) in my cpu report during the job. So this could mean either IO or network could be the bottleneck right? I'll post more details and ganglia reports soon. On Sat, Nov 13, 2010 at 12:26 AM, Jean-Daniel Cryans wrote:

Re: Stats to look out for while running mapreduce jobs with HBase

2010-11-12 Thread Jean-Daniel Cryans
The most important: - no swap, as is zero, none, nada - near 0 io wait Then it's about making sure that you can drive your user CPU to near 100%. If you can't, then you have a bottle neck somewhere and there's no magical way of finding it out. It usually starts by understanding what you're doin

Stats to look out for while running mapreduce jobs with HBase

2010-11-11 Thread Hari Sreekumar
Hi, I am quite new to hadoop and hbase, and I am having a hard time here figuring out some issues with my cluster, and I am pretty sure many of you have gone through many of the problems I am facing right now. I need some help in figuring out what exactly are the bottlenecks in my system. I