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

HBase Major Compaction

PreviousHBase Minor CompactionNextHBase Read Merge

Last updated 5 years ago

Was this helpful?

Major compaction merges and rewrites all the HFiles in a region to one HFile per column family, and in the process, drops deleted or expired cells. This improves read performance; however, since major compaction rewrites all of the files, lots of disk I/O and network traffic might occur during the process. This is called write amplification.

Major compactions can be scheduled to run automatically. Due to write amplification, major compactions are usually scheduled for weekends or evenings. Note that MapR-DB has made improvements and does not need to do compactions. A major compaction also makes any data files that were remote, due to server failure or load balancing, local to the region server.