The disadvantages of the extremely large MAX_FILESIZE

One of our HBase tables has grown to over 1000 regions. We reduced this by changing the MAX_FILESIZE property of the table from the default value from 256 MB to 10 GB. Now we are in up to 70 regions.

I was wondering what would be the side effect of this change? In other words, what are the disadvantages of increasing the MAX_FILESIZE table? What happens if we increase MAX_FILESIZE to 100 GB or even 1 TB?

My initial suspicion is that compression is slowing down significantly, but I want to be sure. What do you guys think?

Thanks!

+4
source share
2 answers

parallelism, , M/R . , HBase : " - . 5 RS , 1000 ."

, - 1000 , 1000 . 2-3 , . , .

+1

2.5.2.6 .

+1

All Articles