-
Notifications
You must be signed in to change notification settings - Fork 5
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
Distributed-Hash-Table DHT #4
Comments
that could be problematic for imagine a database which does small changes in short time I think it would not be so hard to locate the replicat and update them on change |
As I understand PEX sends list of peers for the file and also what each peer what shards they have and what chunks from the sharks (like seeder) The network topology I assume could be also synched with Raft, just we can use PEX for the above shards and chunks metadata But do I get it wrong on what PEX does? |
I would still try with PEX also as seems more reliable and more scalable.
The actual shards (splits of the original file) I would imagine 512MB or 64MB and then from torrent POV each of these shards is seen as a file where yes chunk should be in the order of hundreds of kB |
I agree we don't need PEX but DHT. I think it's more scalable to use DHT instead of a tracker as it eliminates the single point of failure. Will we need to create some service that acts like DHT and reads metadata from tikv? |
Well we can implement it similar to |
https://github.com/radumarias/rfs/wiki/Distributed-Hash-Table-DHT
#39
#3
The text was updated successfully, but these errors were encountered: