Re: How to avoid major compaction during restart?

the balancing for the duration of the restart, which would avoid the need for major compaction afterwards. Marcell On Thu, Jun 28, 2018 at 12:55 PM, Marcell Ortutay wrote: > Hi all, > > I'm interested in ways to avoid a major compaction when restarting all the > HBase region servers

How to avoid major compaction during restart?

Hi all, I'm interested in ways to avoid a major compaction when restarting all the HBase region servers in a cluster (for example, for a version upgrade). Are there any recommended techniques for achieving this? Thanks, Marcell

Re: How to improve HBase read performance.

This ticket: https://issues.apache.org/jira/browse/HBASE-20459 was fixed in the latest version of HBase, upgrading to latest may help with performance On Wed, May 16, 2018 at 3:55 AM, Kang Minwoo wrote: > Hi, Users. > > I store a lot of logs in HBase. > However, the

HBase scans seem slow, compute bound. How to improve?

I'm new to HBase and looking at some performance testing for my use case. I've noticed that HBase scans seem "slow" compared to machine capabilities. Here is a bit more detail on the testing I am running. I have loaded 3 test tables into HBase and sqlite3 for comparison. I'm using sqlite3 as a

HBase range scan seems slow?

Hi all, I'm fairly new to HBase and was a bit surprised by performance I am seeing for a range scan. I am running a range scan over ~3 million rows in an HBase cluster with 4 region servers, each fairly large instances on AWS (24 HDD). I'm pulling a single float value from each row and computing

Re: Want to change key structure

Format in your MR job. > For locality, i dont think you should worry that much because major > compaction usually takes care of it. If you want very high locality from > beginning then you can run a major compaction on new table after your > initial load. > > HTH, > Anil Gupta > > O

Want to change key structure

I have a large HBase table (~10 TB) that has an existing key structure. Based on some recent analysis, the key structure is causing performance problems for our current query load. I would like to re-write the table with a new key structure that performs substantially better. What is the best way