Non-inline Erasure Coding Vs Inline Erasure Coding

Comparison between non-inline erasure coding/scheduled tiering and inline erasure coding/instant tiering.

Non-inline erasure coding refers to the erasure coding that exists pre-8.1. Non-inline erasure coding is called scheduled tiering.
Inline erasure coding is called instant tiering.

The following table compares non-inline erasure coding and inline erasure coding.

NOTE
To migrate existing scheduled EC buckets to Inline Erasure Coding, see Migrating S3 buckets to Inline Erasure Coding (IEC) buckets.
Table 1. Non-inline erasure coding Vs inline erasure coding
Behavior/operation Non-inline erasure coding Inline erasure coding

Data replication

3x until offloaded ~1.5x because of continuous offloads
Data Offload to backend volume scheduled or manually initiated automatic and continuously running
Availability from Data Fabric version 6.2 8.1
Advantages Control over offload scheduling Efficient storage utilization
Disadvantages Requires more storage for front end volume until offloaded. Marginal higher resource consumption
Support for S3 buckets (object store) Yes Yes
Support for files Yes No
Task status as seen on command line The task state, status, progress, offload start, offload end times The task state is always running, last inline erasure coding (IEC) offload attempt, last IEC success timestamps