hbase
  • Introduction
  • Concepts
  • Hbase Architecture
    • Region servers
      • Regions
      • HFile
      • WAL(HLog)
      • How the Components Work Together
      • BlockCache
      • Region Split
      • Store(HStore OR Memstore))
      • HBase Region Flush
    • Special Tables ROOT , META
    • Fault Tolerance( Failover)
    • Data Locality
    • ZooKeeper: The Coordinator
    • HBase HMaster
    • Read Load Balancing
    • HBase Minor Compaction
    • HBase Major Compaction
    • HBase Read Merge
  • Queries
  • HBase Shell
    • Guide Lines
    • overview-example
  • HBase Read
  • HBase Write
  • Known Use Cases
  • HBase Data Model
  • References
  • Hands on
  • Case Studies
  • Notes
Powered by GitBook
On this page

Was this helpful?

  1. Hbase Architecture
  2. Region servers

Region Split

PreviousBlockCacheNextStore(HStore OR Memstore))

Last updated 5 years ago

Was this helpful?

Initially there is one region per table. When a region grows too large, it splits into two child regions.

Both child regions, representing one-half of the original region, are opened in parallel on the same Region server, and then the split is reported to the HMaster. For load balancing reasons, the HMaster may schedule for new regions to be moved off to other servers.