Skip to content
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

Enable Automatic Replication Of Object/Bucket Data #52

Open
bonedaddy opened this issue Apr 17, 2020 · 0 comments
Open

Enable Automatic Replication Of Object/Bucket Data #52

bonedaddy opened this issue Apr 17, 2020 · 0 comments
Labels
low-priority task at hand is low priority as there isn't an immediate need for it

Comments

@bonedaddy
Copy link

The CRDT pr enables high availability of the ledger store, however to get high availability of the actual object/bucket data, TemporalX's replication feature needs to be use. It might be worth enabling "automatic management" of the replication.

One possible implementation would be a background worker process that whenever the ledger is updated, it would update a replication file with the new CID(s), sign it, and publish it. This should be the most efficient option, however there might be a slight delay between the time the ledger is updated, and replication worker picks it up

The faster solution would be that whenever we finish storing the data for the request, we launch a goroutine to handle the replication update broadcast, and then we return the response to the user.

@bonedaddy bonedaddy added the low-priority task at hand is low priority as there isn't an immediate need for it label Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-priority task at hand is low priority as there isn't an immediate need for it
Projects
None yet
Development

No branches or pull requests

1 participant