Metraipolis › archive › dc_71babb67810b
Enabling Differentiated QoS Degradation for Replicated Databases under Failures — arXiv:2608.11836
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2608.11836
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-19T05:31:06.176Z
- SHA-256 of the archived text
cc32f4ac4120b40ce1cee126385f60100f5030c50340135d6ce87377528f9972- Stable URL of this page
https://metraipolis.com/documento/dc_71babb67810b
How to cite
Enabling Differentiated QoS Degradation for Replicated Databases under Failures — arXiv:2608.11836 — arXiv (en), https://arxiv.org/abs/2608.11836 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_71babb67810b (Metraipolis archive dc_71babb67810b, sha256 cc32f4ac4120b40ce1cee126385f60100f5030c50340135d6ce87377528f9972)
BibTeX
@misc{dc71babb67810b,
title = {Enabling Differentiated QoS Degradation for Replicated Databases under Failures — arXiv:2608.11836},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2608.11836},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_71babb67810b; sha256 cc32f4ac4120b40ce1cee126385f60100f5030c50340135d6ce87377528f9972},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.11836. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Elasticity is commonly presented as the default response to capacity loss after failures, since replacement replicas can compensate for failed nodes and restore pre-incident service levels. Replacement capacity entails both delay and additional resource commitment, as replicas must be provisioned and synchronized before they can serve traffic. Under fixed budgets or constrained operating conditions, capacity restoration cannot be treated as the immediate recovery path. Failure handling must instead define how the service continues while capacity remains reduced. When the service exposes differentiated service levels, capacity loss cannot be handled uniformly. Degradation becomes part of the service behavior, requiring explicit control over how reduced capacity affects each class without erasing the intended differentiation. We study differentiated QoS degradation in replicated database services with service-class-aware sessions. We present a repair-to-target policy, implemented in PLB, a PostgreSQL JDBC middleware load balancer for service-class-aware routing. When fail-stop failures remove part of the available capacity, PLB updates the role assignment of healthy replicas into Premium, Mixed, and Freemium roles. This keeps the replica pool shared while ensuring that new session assignments continue to reflect the service class. We evaluate PLB under single and cascading replica failures across two deployment strategies: isolated perclass replica pools and shared, priority-agnostic routing. The results show that PLB improves median Premium goodput retention by 26-28 percentage points under a Premium-side fault, achieves more than 2x higher Premium goodput in the most severe cascading-failure phase, and reduces Premium p95 latency by 18.2% relative to shared round-robin. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-13 in cs.DC). Categorie arXiv: Databases (cs.DB) ; Distributed, Parallel, and Cluster Computing (cs.DC). Pagina del lavoro: https://arxiv.org/abs/2608.11836 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-19T05:15:56.873Z dalla pagina https://arxiv.org/catchup/cs.DC/2026-08-13?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).