Re: phoenix table with 50 salt buckets ( regions ) - now shows as 68 regions and18 of them stale

I did not set any split policy. I was under assumption 'hbase.hregion.max.filesize' => '107374182400' ( 100 GB ) this property would take care and size was also with in 33 GB. I want to understand even if split happens it's of no use, as the first salt byte 1 - 49 are used for putting the keys

Re: phoenix table with 50 salt buckets ( regions ) - now shows as 68 regions and18 of them stale

Did you set the split policy to CostantSizeRegionSplitPolicy? > On Mar 22, 2018, at 2:56 PM, Adi Kadimetla wrote: > > Group, > TABLE - with 50 salt buckets and configured as time series table. > > Having pre split into 50 SALT buckets we disabled the region splits using

phoenix table with 50 salt buckets ( regions ) - now shows as 68 regions and18 of them stale

Group, TABLE - with 50 salt buckets and configured as time series table. Having pre split into 50 SALT buckets we disabled the region splits using max file size as 100 GB for the split. I see some of the keys got split and created stale regions. no writes are happening into the region