[ https://issues.apache.org/jira/browse/HBASE-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zheng Hu updated HBASE-21355: ----------------------------- Description: When testing the branch-2's write performance in our internal cluster, we found that the region will be inexplicably split. We use the default ConstantSizeRegionSplitPolicy and hbase.hregion.max.filesize=40G,but the region will be split even if its bytes size is less than 40G(only ~6G). Checked the code, I found that the following path will accumulate the store's storeSize to a very big value, because the path has no reset.. {code} RsRpcServices#getRegionInfo -> HRegion#isMergeable -> HRegion#hasReferences -> HStore#hasReferences -> HStore#openStoreFiles {code} BTW, we seems forget to maintain the read replica's storeSize when refresh the store files. was: When testing the branch-2's write performance in our internal cluster, we found that the region will be inexplicably split. We use the default ConstantSizeRegionSplitPolicy and hbase.hregion.max.filesize=40G,but the region will be split even if its bytes size is less than 40G(only ~6G). Checked the code, I found that the following path will accumulate the store's storeSize to a very big value, because the path has no reset.. {code} RsRpcServices#getRegionInfo -> HRegion#isMergeable -> HRegion#hasReferences -> HStore#hasReferences -> HStore#openStoreFiles {code} BTW, we seems forget to maintain the read replica's storeSize when openStoreFiles. > HStore's storeSize is calculated repeatedly which causing the confusing > region split > ------------------------------------------------------------------------------------- > > Key: HBASE-21355 > URL: https://issues.apache.org/jira/browse/HBASE-21355 > Project: HBase > Issue Type: Bug > Reporter: Zheng Hu > Assignee: Zheng Hu > Priority: Critical > Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3 > > > When testing the branch-2's write performance in our internal cluster, we > found that the region will be inexplicably split. > We use the default ConstantSizeRegionSplitPolicy and > hbase.hregion.max.filesize=40G,but the region will be split even if its > bytes size is less than 40G(only ~6G). > Checked the code, I found that the following path will accumulate the > store's storeSize to a very big value, because the path has no reset.. > {code} > RsRpcServices#getRegionInfo > -> HRegion#isMergeable > -> HRegion#hasReferences > -> HStore#hasReferences > -> HStore#openStoreFiles > {code} > BTW, we seems forget to maintain the read replica's storeSize when refresh > the store files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)