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

Issues relating to a node being unavailable #385

Closed
tahpot opened this issue Dec 21, 2023 · 1 comment · Fixed by #386
Closed

Issues relating to a node being unavailable #385

tahpot opened this issue Dec 21, 2023 · 1 comment · Fixed by #386
Assignees

Comments

@tahpot
Copy link
Member

tahpot commented Dec 21, 2023

Identified issues:

  1. When the currently connected storage node goes down, any new database changes aren't sync'd with another server
  2. When deleting a database and any node is down, the database deletion fails
  3. When deleting a database and a node is down, when that node comes back online, it doesn't know that database was supposed to be deleted
  4. When a node is down, server to server replication fails
@tahpot tahpot self-assigned this Dec 21, 2023
@tahpot
Copy link
Member Author

tahpot commented Dec 21, 2023

When a node is down, server to server replication fails

This is fixed on storage-node with:

  1. verida/storage-node@d0fa92b
  2. verida/storage-node@a59174f

Requires a redeploy of storage nodes.

This was referenced Dec 21, 2023
@tahpot tahpot closed this as completed Dec 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant