The Case for Custom Storage Backends in Distributed Storage Systems

Citations Over TimeTop 19% of 2020 papers

Abstract

For a decade, the Ceph distributed file system followed the conventional wisdom of building its storage backend on top of local file systems. This is a preferred choice for most distributed file systems today, because it allows them to benefit from the convenience and maturity of battle-tested code. Ceph’s experience, however, shows that this comes at a high price. First, developing a zero-overhead transaction mechanism is challenging. Second, metadata performance at the local level can significantly affect performance at the distributed level. Third, supporting emerging storage hardware is painstakingly slow. Ceph addressed these issues with BlueStore, a new backend designed to run directly on raw storage devices. In only two years since its inception, BlueStore outperformed previous established backends and is adopted by 70% of users in production. By running in user space and fully controlling the I/O stack, it has enabled space-efficient metadata and data checksums, fast overwrites of erasure-coded data, inline compression, decreased performance variability, and avoided a series of performance pitfalls of local file systems. Finally, it makes the adoption of backward-incompatible storage hardware possible, an important trait in a changing storage landscape that is learning to embrace hardware diversity.

Related Papers

• → On distributed object storage architecture based on mimic defense(2021)6 cited
• Distributed Spatial Data Storage Object(2006)
• → An object-based storage model for distributed remote sensing images(2006)2 cited
• → A Method of Recovering HBase Records from HDFS Based on Checksum File(2017)1 cited
• → BIG DATA STORAGE SUSTAINABILITY MODEL IN A DISTRIBUTED FILE SYSTEM(2022)