New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload syncs to closest node #48
Comments
This was referenced Apr 7, 2020
This was referenced Apr 15, 2020
acud
added a commit
that referenced
this issue
Apr 17, 2020
1 task
acud
added a commit
that referenced
this issue
Apr 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic
Story
As a user of Swarm, I want that my chunk is stored at the node whose address is closest to the address of the chunk, such that anybody who requests the chunk afterwards, knows where to find this chunk.
Background
Full connectivity
This epic can be fulfilled on a full-connectivity network. The node who uploads a chunk looks in his address book for the node whose address is closest to the address of the chunk. In a full connectivity network, this happens to be the node who is closest to the address of the chunk. In a partial connectivity network (i.e. Kademlia), this may or may not be the node who is closest to the address of the chunk. From the perspective of the node, however, this doesn't matter. He just forwards the push sync request to the connected node who is closest to the address of the chunk.
Note on pricing
For this epic, it will be sufficient to upload the chunk to the closest connected node. However, in the future, there might be a possibility where the closest connected node is not the node to whom we should forward the push-sync, if there is a node who is further away, but cheaper.
See (picture from BOS):
Acceptance criteria
Dependencies
SyncPeer
methodSyncPeer
Protocol test vectors:
toplogy.ErrWantSelf
)The text was updated successfully, but these errors were encountered: