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

Read Load Balancing

PreviousHBase HMasterNextHBase Minor Compaction

Last updated 5 years ago

Was this helpful?

Splitting happens initially on the same region server, but for load balancing reasons, the HMaster may schedule for new regions to be moved off to other servers. This results in the new Region server serving data from a remote HDFS node until a major compaction moves the data files to the Regions server’s local node. HBase data is local when it is written, but when a region is moved (for load balancing or recovery), it is not local until major compaction.