Hi, Srinidhi
Next time you will see this issue, take jstack of a RS several times in a
row. W/o stack traces it is hard
to tell what was going on with your cluster after upgrade.
-Vlad
On Tue, Sep 4, 2018 at 3:50 PM Srinidhi Muppalla
wrote:
> Hello all,
>
> We are currently running Hbase 1.3
Manjeet -- you are still missing the fact that if you do not split your
table into multiple regions, your data will not be distributed.
Why do you think that your rowkey design means you can't split your table?
On 9/3/18 6:09 AM, Manjeet Singh wrote:
Hi Josh
Sharing steps and my findings for
Hello all,
We are currently running Hbase 1.3.0 on an EMR cluster running EMR 5.5.0.
Recently, we attempted to upgrade our cluster to using Hbase 1.4.4 (along with
upgrading our EMR cluster to 5.16). After upgrading, the CPU usage for all of
our region servers spiked up to 90%. The load_one for
