Thanks! Doug. I am not absolutely new to hbase. Like in Kevin's email, because of mapred job (hive) contention, hbase regionservers die and whole hbase go down.
I understand that we have to somehow logically or physically separate the clusters.
From: Doug Meil [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2013 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: Just joined the user group and have a question
If you're absolutely new to Hbase, you might want to check out the Hbase refGuide in the architecture, performance, and troubleshooting chapters first.
In terms of determining why your region servers "just die", I think you need to read the background information then provide more information on your cluster and what you're trying to do because although there are a lot of people on this dist-list that want to help, you're not giving folks a whole lot to go on.
On 1/17/13 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?