[
https://issues.apache.org/jira/browse/HBASE-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014971#comment-15014971
]
Josh Elser commented on HBASE-14838:
------------------------------------
bq. Because code which calculates region size in region normalizer uses metrics
(ServerLoad/RegionLoad based), where region size (aggregated store file size)
is represented is MB and is floored (truncated) down
You're the best. Saved me some digging :)
bq. So how should we proceed here on this jira? Add a javadoc comment to
specify that pre-split tables are not touched if they are empty?
I think that would be a good addition. I can add something to the class-level
javadocs.
> SimpleRegionNormalizer does not merge empty region of a table
> -------------------------------------------------------------
>
> Key: HBASE-14838
> URL: https://issues.apache.org/jira/browse/HBASE-14838
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Romil Choksi
>
> SImpleRegionNormalizer does not merge empty region of a table
> Steps to repro:
> - Create an empty table with few, say 5-6 regions without any data in any of
> them
> - Verify hbase:meta table to verify the regions for the table or check
> HMaster UI
> - Enable normalizer switch and normalization for this table
> - Run normalizer, by 'normalize' command from hbase shell
> - Verify the regions for table by scanning hbase:meta table or checking
> HMaster web UI
> The empty regions are not merged on running the region normalizer. This seems
> to be an edge case with completely empty regions since the Normalizer checks
> for: smallestRegion (in this case 0 size) + smallestNeighborOfSmallestRegion
> (in this case 0 size) > avg region size (in this case 0 size)
> thanks to [~elserj] for verifying this from the source code side
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
