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

Online-upgrade of GraphDB (or whatever we use in the future) #1553

Open
subotic opened this issue Dec 10, 2019 · 1 comment
Open

Online-upgrade of GraphDB (or whatever we use in the future) #1553

subotic opened this issue Dec 10, 2019 · 1 comment
Labels
question further information is requested

Comments

@subotic
Copy link
Collaborator

subotic commented Dec 10, 2019

There is a strong possibility that we will need to host around 150 new projects each year, so our current strategy of shutting down knora-api (or the planned one with read-only mode) will not work. With these project numbers and the accompanied triplestore size, this strategy would probably shut us down for a few days.

So, either triplestore upgrades are an exceptional occurrence ( e.g., once a year), or we need to find a way to accomplish them while upholding normal operation.

Any suggestions are welcome.

@benjamingeer
Copy link

An online upgrade would have to be done in a transaction. But GraphDB only allows one update transaction at a time. So, while an update is occurring, you are effectively in read-only mode in any case, because all other updates have to wait.

@subotic subotic added this to the Backlog milestone Feb 7, 2020
@irinaschubert irinaschubert removed this from the Backlog milestone Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question further information is requested
Projects
None yet
Development

No branches or pull requests