Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Just joined the user group and have a question


Copy link to this message
-
RE: Just joined the user group and have a question
Hi Kevin,

Thanks for the reply.  Currently using 10 mappers and 10 reducers on each node.  With 32 GB memory, allotted 2 GB for hbase heapsize, mapred.map.child.java.opts and reduce.child.java.opts is 1 GB, and therefore having 10 mappers and 10 reducers looks like not a bad idea.

>From what you are saying, I can only use 10 MR(12-2)( meaning 6 mappers and 4 reducers??? Or 8 and 2 or 5 and 5?), is it not very few?

I would also want to test separating MR and hbase by running TT on some and region server on some like I thought.  Also thinking of separating clusters as well.  In that case we can get higher cpu servers for hbase.  

Only after adding hbase to the hadoop cluster, we are seeing stability issues and that is the reason trying to find out the working solution.

Thanks for your time,
Chalcy

-----Original Message-----
From: Kevin O'dell [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2013 12:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Just joined the user group and have a question

Chalcy,

  Glad to have you aboard. One thing to look at is your max map and reduce slots that you are currently allowing. Typically, we look at the CPU architecture and say if it is not HT(hyperthreaded) then it is a 1:1, if it is using HT 1:1.5. Dual quad core without HT you would be able to use 8 total MR slots, but since you have HBase you should give your self a couple slots. This means only using 6 MR slots. Dual quad core with HT you would have 16 logical cores, you could use 12 MR slots, but since you have HBase you want to leave a couple cores. This means only using 9 or 10 slots for MR. This can help with some of the pressure from using MR/hive/pig on the same cluster.

  As for separating MR and HBase. You could break down your processes so that TT run on some nodes and RS run on others, but typically people will setup two separate clusters.
On Thu, Jan 17, 2013 at 12:24 PM, Chalcy Raja <[EMAIL PROTECTED]
> wrote:

> Hi HBASE Gurus,
>
>
>
> I am Chalcy Raja and I joined the hbase group yesterday.  I am already
> a member of hive and sqoop user groups.  Looking forward to learn and
> share information about hbase here!
>
>
>
> Have a question:  We have a cluster where we run hive jobs and also hbase.
>  There are stability issues like region servers just die.  We are
> looking into fine tuning.  When I read about performance and also
> heard from another user is separate mapreduce from hbase.  How do I do
> that?  If I understand that as running tasktrackers on some and hbase
> region servers on some, then we will run into data locality issues and
> I believe it will perform poorly.
>
>
>
> Definitely I am not the only one running into this issue.  Any
> thoughts on how to resolve this issue?
>
>
>
> Thanks,
>
> Chalcy
>

--
Kevin O'Dell
Customer Operations Engineer, Cloudera
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB