Ceph in Production: RBD, RGW and CephFS
A field guide to Ceph in production: which surface serves which workload, what failure domains cost in replicas, how the upgrade lifecycle really rolls back, and what key rotation does not do.
A field guide to Ceph in production: which surface serves which workload, what failure domains cost in replicas, how the upgrade lifecycle really rolls back, and what key rotation does not do.
Size an object store against bytes, object metadata, request demand and maintenance time. A practical worksheet for small files, retention, erasure coding and release-channel choices.
The 405 storm had three root defects in the delete-marker path. PR #162 fixed the first attempt; PR #184 fixes retries, purge status and MRF healing in the Silo fork.
MinIO Community Edition has had no release since October 2025 and the repository is archived. Three CVEs will never be patched there. Here is how to assess what your cluster is actually exposed to, and where the maintained community fork fits in.
HEAD probes on delete markers answer 405 and replication counts that as success. 20M stuck versions turned the loop into 684M useless requests in 48 h.
During a MinIO replication incident three of the signals you reach for mislead you. The 405 on HeadObject is the success path, a retried 429 is invisible, and worker queue overflow logs nothing under the default priority. The counter that tracks dropped objects is incremented in four places and read in none.
Ceph 20.2.4 and 19.2.6 patch four authentication and authorization CVEs. The remediation also needs CephX key rotation, client checks, and RGW multisite planning.
Compression, object population and request count measure different things. Compare point-cloud packaging, range reads, update costs and cleanup with an explicit synthetic sizing example.
A successful source PUT does not establish a recoverable peer copy. Separate MinIO site-replication acknowledgment, persisted retry state and catch-up capacity before committing to an RTO or RPO.
MinIO has no NameNode. It puts the namespace on XFS as real directories and xl.meta files. On Lots of Small Files that means you can exhaust inodes while df -h still looks fine, and a flat leaf can stall PUT, LIST, scanner, and ILM together. Here is the on-disk model, the inode math, and a prefix recipe that keeps XFS inside a regime you can operate.