Implementing Decentralized Per-Partition Automatic Failover in Azure Cosmos DB
Fuente:
arXiv
Salvato in:
| Autori principali: | , , , , , , , , , |
|---|---|
| Natura: | Preprint |
| Pubblicazione: |
2025
|
| Soggetti: | |
| Accesso online: | |
| Tags: |
Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
|
| _version_ | 1866913849755566080 |
|---|---|
| author | Rowe, Josh Horal, Mikael Sundar, Hari Sudan Arumugam, Muthukumaran Kose, Burak Palivela, Sravani Mitra Marsh, Geni Jain, Varun Kumar, Abhishek Patel, Dhaval |
| author_facet | Rowe, Josh Horal, Mikael Sundar, Hari Sudan Arumugam, Muthukumaran Kose, Burak Palivela, Sravani Mitra Marsh, Geni Jain, Varun Kumar, Abhishek Patel, Dhaval |
| contents | Azure Cosmos DB is a cloud-native distributed database, operating at a massive scale, powering Microsoft Cloud. Think 10s of millions of database partitions (replica-sets), 100+ PBs of data under management, 20M+ vCores. Failovers are an integral part of distributed databases to provide data availability during outages (partial or full regional outages). While failovers within a replica-set within a single region are well understood and commonly exercised, geo failovers in databases across regions are not as common and usually left as a disaster recovery scenario. An upcoming release of Azure Cosmos DB introduces a fine grained (partition-level) automatic failover solution for geo failovers that minimizes the Recovery Time Objective (RTO) and honors customer-chosen consistency level and Recovery Point Objective (RPO) at any scale. This is achieved thanks to a decentralized architecture which offers seamless horizontal scaling to allow us to handle outages ranging from node-level faults to full-scale regional outages. Our solution is designed to handle a broad spectrum of hardware and software faults, including node failures, crashes, power events and most network partitions, that span beyond the scope of a single fault domain or an availability zone. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2505_14900 |
| institution | arXiv |
| publishDate | 2025 |
| record_format | arxiv |
| spellingShingle | Implementing Decentralized Per-Partition Automatic Failover in Azure Cosmos DB Rowe, Josh Horal, Mikael Sundar, Hari Sudan Arumugam, Muthukumaran Kose, Burak Palivela, Sravani Mitra Marsh, Geni Jain, Varun Kumar, Abhishek Patel, Dhaval Databases H.2.4; H.2.7 Azure Cosmos DB is a cloud-native distributed database, operating at a massive scale, powering Microsoft Cloud. Think 10s of millions of database partitions (replica-sets), 100+ PBs of data under management, 20M+ vCores. Failovers are an integral part of distributed databases to provide data availability during outages (partial or full regional outages). While failovers within a replica-set within a single region are well understood and commonly exercised, geo failovers in databases across regions are not as common and usually left as a disaster recovery scenario. An upcoming release of Azure Cosmos DB introduces a fine grained (partition-level) automatic failover solution for geo failovers that minimizes the Recovery Time Objective (RTO) and honors customer-chosen consistency level and Recovery Point Objective (RPO) at any scale. This is achieved thanks to a decentralized architecture which offers seamless horizontal scaling to allow us to handle outages ranging from node-level faults to full-scale regional outages. Our solution is designed to handle a broad spectrum of hardware and software faults, including node failures, crashes, power events and most network partitions, that span beyond the scope of a single fault domain or an availability zone. |
| title | Implementing Decentralized Per-Partition Automatic Failover in Azure Cosmos DB |
| topic | Databases H.2.4; H.2.7 |
| url | https://arxiv.org/abs/2505.14900 |