Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

FlushLargeStoresPolicy lower bound vs lower bound min?

FlushLargeStoresPolicy lower bound vs lower bound min?

Super Guru

Basically a follow up to another HCC question here.

what is the difference between hbase.hregion.percolumnfamilyflush.size.lower.bound and

hbase.hregion.percolumnfamilyflush.size.lower.bound.min ? or are they used together and if so how?

1 REPLY 1
Highlighted

Re: FlushLargeStoresPolicy lower bound vs lower bound min?

Super Collaborator

InHBASE-14906 we use "hbase.hregion.memstore.flush.size/column_family_number" as the default threshold for memstore flush instead of the fixed value through "hbase.hregion.percolumnfamilyflush.size.lower.bound" property, which makes the default threshold more flexible to various use case. We also introduce a new property in name of "hbase.hregion.percolumnfamilyflush.size.lower.bound.min" with 16M as the default value to avoid small flush in cases like hundreds of column families.

After this change setting "hbase.hregion.percolumnfamilyflush.size.lower.bound" in hbase-site.xml won't take effect anymore, but expert users could still set this property in table descriptor to override the default value just as before