Implement atomic access compatible with key transfers
Closed this issue · 2 comments
zllovesuki commented
in concurrent kv operations while nodes are joining and leaving, it is possible that keys are transferred, but the network does not know about the new/old node yet. therefore, a concurrent kv could still be serviced by the old successor, causing lookup to fail.
possible solution: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.71.6111&rep=rep1&type=pdf
this must be resolved before we can put certmagic.Storage on DHT
zllovesuki commented
2030fed partially unblocks this issue by providing key consistency during join/leave + concurrent kv operations
zllovesuki commented
supposedly implemented in c311064, however more testing is required