Pepitedata
  • Home
  • Services
  • Audits
  • Expert Call
  • About
  • Blog
  • Contact

site replication

Two bars comparing a short claimed recovery duration with a far longer measured one interrupted by a waiting gap
data

Data Platform Resilience: RTO, RPO and Replication in Practice

A DR document states minutes and megabytes. Replication architecture delivers a convergence time, a single-copy window and a failed tail. This guide maps what actually decides your RTO and RPO.

By Julien Laurenceau, 5 days2026-09-30 ago
Three server racks labeled A, B and C joined by a closed oval conveyor loop where one amber crate labeled 405 circulates endlessly, never docking at the open slot on rack C
MinIO

MinIO delete-marker convergence: how the Silo fork fixed the 405 replication loop

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.

By Julien Laurenceau, 3 weeks2026-09-15 ago
Two MinIO sites locked in a closed replication loop: delete markers stamped 405 circulate endlessly between two racks, piling up instead of converging
MinIO

MinIO site replication bug: how 684 million HTTP 405s exposed the delete-marker loop

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.

By Julien Laurenceau, 4 weeks2026-09-06 ago
Abstract illustration of multi-site object storage replication between data centers
MinIO

MinIO Site Replication: Sync Mode Will Not Save Your RPO

MinIO site replication has no cross-site quorum, and its replication queue exists only inside the source cluster: lose that site and the un-replicated backlog is gone and un-enumerable. Sync mode costs latency without fixing that. The precise model, the RTO/RPO table, and the DR patterns that match real SLAs.

By Julien Laurenceau, 2 months2026-08-03 ago
Diagram: MinIO erasure-coding storage inflation on small objects: per-drive xl.meta metadata replicated across the erasure set
data

Stop using MinIO as a NoSQL database: why S3 object stores collapse on small-file workloads

Two MinIO platforms, same root cause: used as a NoSQL store. Field notes on LIST IOPS, XFS directory limits, scanner & heal SLAs, the erasure-coding storage-efficiency inversion on small objects, and why Apache Cassandra (or Ceph) is the right answer on-prem in 2026.

By Julien Laurenceau, 5 months2026-05-17 ago
  • Privacy Policy
  • Mentions légales
  • CGV
  • Cookies
Hestia | Developed by ThemeIsle