Advantages, disadvantages, and requirements for erasure coding

Before deciding whether to use replication or erasure coding to protect object data from loss, you should understand the advantages, disadvantages, and the requirements for erasure coding.

Advantages of erasure coding

When compared to replication, erasure coding offers improved reliability, availability, and storage efficiency.
  • Reliability: Reliability is gauged in terms of fault tolerance—that is, the number of simultaneous failures that can be sustained without loss of data. With replication, multiple identical copies are stored on different nodes and across sites. With erasure coding, an object is encoded into data and parity fragments and distributed across many nodes and sites. This dispersal provides both site and node failure protection. When compared to replication, erasure coding provides improved reliability at comparable storage costs.
  • Availability: Availability can be defined as the ability to retrieve objects if Storage Nodes fail or become inaccessible. When compared to replication, erasure coding provides increased availability at comparable storage costs.
  • Storage efficiency: For similar levels of availability and reliability, objects protected through erasure coding consume less disk space than the same objects would if protected through replication. For example, a 10 MB object that is replicated to two sites consumes 20 MB of disk space (two copies), while an object that is erasure coded across three sites with a 6+3 erasure coding scheme only consumes 15 MB of disk space.
    Note: Disk space for erasure coded objects is calculated as the object size plus the storage overhead. The storage overhead percentage is the number of parity fragments divided by the number of data fragments.

Disadvantages of erasure coding

When compared to replication, erasure coding has the following disadvantages:
  • Increased number of Storage Nodes and sites required. For example, if you use an erasure coding scheme of 6+3, you must have at least three Storage Nodes at three different sites. In contrast, if you simply replicate object data, you require only one Storage Node for each copy.
  • Increased retrieval latencies when you use erasure coding across geographically distributed sites. The object fragments for an object that is erasure coded and distributed across remote sites take longer to retrieve over WAN connections than an object that is replicated and available locally (the same site to which the client connects).
  • When you use erasure coding across geographically distributed sites, higher WAN network traffic usage for retrievals and repairs, especially for frequently retrieved objects or object repairs over WAN network connections.
  • Higher usage of compute resources.

Requirements for erasure coding

Erasure coding is best suited for the following requirements:
  • Objects larger than 1 MB in size.
    Attention: Due to the overhead of managing the number of fragments associated with an erasure coded copy, do not use erasure coding for objects smaller than 200 KB.
  • Long-term or cold storage for infrequently retrieved content.
  • High data availability and reliability.
  • Protection against complete site and node failures.
  • Storage efficiency.
  • Single-site deployments that require efficient data protection with only a single erasure-coded copy rather than multiple replicated copies.