Zum Hauptinhalt springen
Podcasts & Audio BriefingsTechLinked: BIG OOF(20.10.2026 um 03:06 Uhr)
•••••••
Sicherheitslücken (CVE)CVE-2020-17160 | Microsoft Azure Sphere protection mechanism(20.10.2026 um 03:08 Uhr)
•••
Podcasts & Audio BriefingsTechLinked: BIG OOF(20.10.2026 um 03:06 Uhr)
•••••••
Sicherheitslücken (CVE)CVE-2020-17160 | Microsoft Azure Sphere protection mechanism(20.10.2026 um 03:08 Uhr)
•••
Intelligence View
⚡ tsecurity.de Intelligence

USENIX: OSDI '26 - WriteGuards: Distributed Storage Support for Strongly Consistent Caches

Video von USENIX auf YouTube: OSDI '26 - WriteGuards: Distributed Storage Support for Strongly Consistent Caches Ziming Mao, University of California…

HD Video
OSDI '26 - WriteGuards: Distributed Storage Support for Strongly Consistent Caches
Video abspielen
Beitrag
0
Seite
0
↗ Quelle (USENIX)
Social ReaktionenReagiere als Erste:r — dein Feedback zählt!

YouTube Video

OSDI '26 - WriteGuards: Distributed Storage Support for Strongly Consistent Caches



Ziming Mao, University of California, Berkeley; Atul Adya and Jonathan Ellithorpe, Databricks; Rishabh Iyer and Matei Zaharia, University of California, Berkeley; Scott Shenker, University of California, Berkeley and ICSI; Ion Stoica, University of California, Berkeley



This paper presents a set of in-process and remote distributed caches for datacenter environments, CLINK and CRINK respectively, that provide linearizable reads entirely from memory without contacting storage. These caches remain loosely coupled to the storage layer and achieve high performance, scale, and availability by cooperating with auto-sharders and by tracking consistency metadata at the granularity of key ranges rather than individual keys. To our knowledge, CLINK is the first distributed linked cache that delivers scalable, linearizable reads from memory while remaining loosely coupled with storage. At the heart of these caches is a lightweight storage primitive called WriteGuards that can be easily added to a distributed store. WriteGuards prevent a subtle race we call the delayed-writes anomaly arising during changes in ownership of key ranges. Each write carries a small fencing value tied to the current owner, and the storage system checks this value to reject delayed writes. WriteGuards apply to key ranges instead of individual keys for scalability, add only a conditional check on the write path, and require no coordination on reads. We implemented our cache designs on TiDB. The in-process cache CLINK cuts tail read latency by three orders of magnitude, and the remote cache CRINK reduces it by 2.2−2.4× relative to direct storage access and existing strongly consistent remote caches.



View the full OSDI '26 program at https://www.usenix.org/conference/osdi26/technical-sessions
Intelligence Digest — free The top security news daily · unsubscribe anytime
Community Rating & Social Proof
⭐ Leser-Wertung
–
Ø / 5.0
No reader ratings yet
Was this page helpful?
0
Jetzt Bewertung abgeben
🟢 Niedrig (1-3.9) 🟡 Mittel (4.0-6.9) 🔴 Hoch (7.0-8.9) Kritisch (9.0-10.0)

Related story clusters & sources (vector AI)

Pull to refresh
Nächster Beitrag