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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 Enhancement: Make migrations not block everything during the process #8278

Open
2 tasks done
DH-555 opened this issue Jun 16, 2024 · 0 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@DH-555
Copy link
Contributor

DH-555 commented Jun 16, 2024

馃敄 Enhancement description

Make the migration procedure start migrating the first/most crucial elements
(for example, recent active users, latest database documents, etc).

And prevent it from blocking practically the entire instance
(although some data could be missing, etc. during the migration, the app will still be somewhat usable as the latest things are available).

An alternative could be a 0 downtime procedure, but it's more complex obviously.

馃帳 Pitch

Current migration procedure blocks the entire appwrite instance meanwhile the script is being run.

This is not a problem in a small app, but if you have a chat-like or similar app where you have thousands of documents, each time it's needed to upgrade, a big disruption is caused leaving the users without access during several minutes.

馃憖 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

馃彚 Have you read the Code of Conduct?

@DH-555 DH-555 added the enhancement New feature or request label Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant