Thanks, will take a look. We're using HBase 1.4.0 on AWS EMR.
Cheers.
Saad
On Tue, Mar 20, 2018 at 9:32 PM, Ted Yu wrote:
> Saad:
> You didn't mention the version of hbase you are using.
> Please check the version to see if the following were included:
>
> HBASE-18164 Fast locality compu
Hi,
We are using HBase 1.4.0 on AWS EMR based Hbase. Since snapshots are in S3,
they take much longer than when using local disk. We have a cron script to
take regular snapshots as backup, and they fail quite often on our largest
table which takes close to an hour to complete the snapshot.
The on
Saad:
You didn't mention the version of hbase you are using.
Please check the version to see if the following were included:
HBASE-18164 Fast locality computation in balancer
HBASE-16570 Compute region locality in parallel at startup
HBASE-15515 Improve LocalityBasedCandidateGenerator in Balancer
Please consider tuning the following parameters of stochastic load balancer
:
"hbase.master.balancer.stochastic.maxRunningTime"
default value is 30 seconds. It controls the duration of runtime for
each balanceCluster()
call.
"hbase.balancer.period"
default is 300 seconds. It controls the maximu
Hi,
We are using the stochastic load balancer, and have tuned it to do a
maximum of 1% of regions in any calculation. But it is way too conservative
after that, it moves one region at a time. Is there a way to tell it to go
faster with whatever number of regions it decided to do? I have been
looki
