Skip to main content

Understanding HBase Cross-Cluster Replication for Disaster Recovery

By Anonymous
Struggling with delivery, architecture alignment, or platform stability?

I help teams fix systemic engineering issues: processes, architecture, and clarity.
→ See how I work with teams.


HBase cross-cluster replication provides asynchronous disaster recovery by streaming WAL edits from a source cluster to one or more destination clusters. It is not a high-availability solution—applications must handle failover logic. This updated guide explains replication modes, requirements, configuration steps and operational considerations for modern HBase deployments.

HBase offers built-in multi-site replication for disaster recovery (DR). Replication streams write-ahead log (WAL) edits from one cluster to another cluster or a set of clusters. Because replication is asynchronous, it does not provide automatic failover or zero-data-loss guarantees; applications must handle HA logic at the architectural level.

Replication Topologies

Modern HBase supports several replication patterns:

  • Master → Slave: a primary cluster replicates edits to one or more secondary clusters. Simple and widely used for DR.
  • Master ↔ Master: two clusters replicate to each other. HBase prevents loops via cluster IDs and mutation tracking.
  • Cyclic Replication: multiple clusters replicate in a ring or mesh, combining master-slave and master-master relationships.

The choice of topology depends on consistency requirements, operational workflows and failover plans.

How Replication Works

Replication is WAL-based. Each RegionServer tails its WAL, identifies edits marked for replication and sends them to the target cluster’s RegionServers. Replication does not copy table definitions—only WAL edits—so the target must be pre-configured with matching schema objects.

Key Requirements and Best Practices

  • Version compatibility: All clusters must run compatible HBase and HDFS versions. Cross-version replication between major releases is not supported.
  • Independent ZooKeeper ensembles: Do not share ZooKeeper between clusters. Each HBase deployment needs its own quorum.
  • Full network connectivity: Every RegionServer in cluster A must reach every RegionServer in cluster B, including ZooKeeper access.
  • Matching schemas: All replicated tables and column families must exist on all clusters with identical names and settings.
  • WAL settings: Ensure WAL compression and encryption settings are compatible across clusters. Some features may not replicate seamlessly depending on the version.
  • Deletes and TTLs: Consider increasing TTL and minimum versions on DR clusters to retain more history and support recovery scenarios.

Enabling Replication

Step 1: Enable replication in configuration

Set the following property on every cluster participating in replication: 

hbase.replication = true

Step 2: Enable replication on the column family

From the HBase shell: 

alter 'your_table', { NAME => 'family_name', REPLICATION_SCOPE => '1' }

A replication scope of 1 marks WAL edits for replication.

Step 3: Add a replication peer

add_peer '1', "zk1,zk2,zk3:2181:/hbase-backup"

List peers: 

list_peers

Operational Considerations

Disaster recovery clusters often retain more history:

  • Increase TTL on replicated tables
  • Increase MIN_VERSIONS to preserve older cells

To disable a peer: 

disable_peer '1'

Disabling replication does not remove previously replicated edits. To fully reset state, logs must be rolled and the peer re-added. Procedures vary by HBase version; use the appropriate WAL roll command or administrative API for your distribution.

Important Notes

  • Replication is asynchronous; applications must manage failover, consistency checks and cutover workflows.
  • Bulk loads, snapshots and filesystem-level copies are not automatically replicated unless specifically integrated.
  • Rolling upgrades must maintain version compatibility across all clusters to avoid replication stalls.

References

Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Building a Model-Agnostic Multi-Agent System with OpenClaw

By
Over one week we rebuilt our AI stack around OpenClaw’s multi-agent architecture to avoid provider lock-in and stop wasting premium tokens. By aligning models to tasks, diversifying fallbacks across providers, enforcing minimal tool access, and switching to memory-first workflows with ephemeral sessions, we reduced token usage per task by about 70% and cut our monthly bill by 77% while improving operational resilience. How We Achieved 77% Cost Reduction and Provider Independence Over the past week, we rebuilt our AI infrastructure around OpenClaw’s multi-agent architecture. The result was a 77% cost reduction , provider independence , and a delegation system that routes work to the most cost-effective model for each job. Below is the technical journey of optimizing a 7-agent squad with OpenClaw. The Challenge: Model Provider Lock-In We started with a simple problem: our entire squad defaulted to a single model provider. This created three issues: Cost inefficiency beca...
Read more

BacNet => MQTT in Production: The Real Cost of Bridging BACnet to MQTT at Scale

By
bacnet2mqtt looks simple in a README and expensive in production. Once BACnet polling, reconnection behavior, stale state, and MQTT publishing collide, teams discover they are not deploying a lightweight adapter but operating infrastructure. This article breaks down where bacnet2mqtt works, where it becomes a bottleneck, and which production patterns reduce the operational damage before incidents, backlogs, and silent data loss turn a building integration into a long-running engineering problem. I inherited a building controls integration problem 18 months ago. Three office floors. 217 BACnet sensors covering temperature, occupancy, and HVAC actuators. The data was trapped inside the building automation network while the business wanted analytics, reporting, and compliance visibility in the data platform. The obvious answer looked easy enough: deploy bacnet2mqtt, bridge BACnet into MQTT, and push the stream into the lakehouse stack. The repository made it sound like a w...
Read more

Connect BACnet to the Cloud with bacnet-mqtt-gateway

By
The bacnet-mqtt-gateway project is an open source protocol bridge that translates BACnet building automation traffic into MQTT messages for cloud and IoT systems. It provides discovery, polling, bidirectional writes, APIs, security, and easy deployment via Docker. Many enterprises struggle to unify BACnet with modern data pipelines and cloud platforms because BACnet is local-network only and not cloud ready. This gateway provides a scalable, secure, production-ready adapter for MQTT ecosystems and smart building integrations. The Problem with BACnet Building automation runs on BACnet . HVAC controllers, lighting systems, metering equipment: they all speak ASHRAE 135 . The protocol handles local control loops well. It fails at cloud ingress. BACnet relies on UDP broadcasts. These do not route over the internet or into VPCs. Your chiller controller cannot talk to AWS IoT Core . Your VAV box cannot publish to an MQTT broker. The air gap between operational technology and modern cl...
Read more