Affects Version/s: 0.94.5, 0.99.0
Fix Version/s: None
In HbaseConfiguration.checkForClusterFreeMemoryLimit it does a check to see if the blockCache + memstore > .8 this threshold ensures we do not run out of memory.
But MemStoreFlusher.getMemStoreLimit does this check:
In our cluster we had the block cache set to an upper limit of 0.76 and the memstore upper limit was set to 0.04. We noticed the memstore size was exceeding the limit we had set and after looking at the getMemStoreLimit code it seems that the memstore upper limit is sized to the default value if the configuration value is less than .1 or greater than .9. This now makes the block cache and memstore greater than our available heap.
We can remove the check for the greater than 90% of the heap as this can never happen due to the check in HbaseConfiguration.checkForClusterFreeMemoryLimit()
This check doesn't seem necessary anymore as we have the HbaseConfiguration class checking for the cluster free limit. Am I correct in this assumption?
|Affects Version/s||0.99.0 [ 12325675 ]|
|Component/s||BlockCache [ 12323302 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|