The ec_enablement_check in NCC generates an informational recommendation to enable erasure coding whenever it estimates meaningful space savings, but this recommendation does not account for the workload's data-change pattern. Erasure coding is a post-process feature intended for write-cold, write-once-read-many (WORM) data such as backups and archives, since it must recompute parity strips whenever data changes, which is costly for actively modified data. VDI environments are inherently write-intensive due to base image deltas, user profile writes, and frequent guest OS changes, so they do not match the WORM profile that erasure coding is designed for. Because this cluster hosts VDI workloads rather than WORM workloads, the administrator should disregard the NCC recommendation to enable erasure coding rather than applying it to either the SelfServiceContainer or the default container.
Community Discussion