Hacker News new | past | comments | ask | show | jobs | submit login
NetChain: Scale-free sub-RTT coordination (acolyer.org)
33 points by signa11 on May 1, 2018 | hide | past | web | favorite | 5 comments



I'd like to understand how this system deals with failed writes. I.e. if a switch fails while a write is in progress, is it guaranteed that the in-progress write either becomes fully visible or not visible at all after the reconfiguration? How is this achieved?

For example, if the head switch fails while the write is being applied on it, it's not obvious to me how the system would still guarantee that the write would not be lost.

On the other hand, if the tail switch fails while the write is being applied on it, there must be some kind of rollback mechanism during the reconfiguration phase to remove the dirty write from all the preceding switches, no? Can somebody point me to the relevant section of the paper that describes how this works?


Suggested reads: vertical paxos and primary backup replication protocols


and the actual paper is available here: https://www.usenix.org/system/files/conference/nsdi18/nsdi18...


What's the catch?


1. You need to control your network equipment (and requires expensive programmable switches)

2. Only single key "transactions"

3. Only small values (IIRC <200bytes)




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: