Why it matters

EC saves HBase storage significantly for cold data. Understanding shapes cost-efficient archives.

Advertisement

The architecture

Replication: 3x storage. EC (RS-6-3): 1.5x. RS-10-4: 1.4x.

Cold HBase HFiles: candidates for EC.

HBase + EC strategy3x replicationhot dataEC 1.4-1.5xcold dataStorage policyper HFileEC recovery is expensive; use only for genuinely cold data
EC + HBase.
Advertisement

How it works end to end

Policy per column family / table: hot data replicated, cold EC.

Read latency: EC blocks slower due to reconstruction.

Recovery: EC data recovery expensive.