You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During one of our deployments, we noticed that the hydra db migration 'CREATE INDEX' step took too long while holding a write lock to the database. Since this is a database serving live traffic, we cannot afford to have a long down time.
Describe your ideal solution
Can we consider adding CONCURRENTLY to the CREATE INDEX sql statements, so that the db can still function while creating the indexes?
Workarounds or alternatives
We considered running hydra janitor commands regularly, but it didn't help much and we also really want to have near zero down time.
Version
master
Additional Context
No response
The text was updated successfully, but these errors were encountered:
We can consider that in the future, but online migrations are generally not available when self-hosting open source and only available when using a build from our Ory Enterprise License. This is because releases in OSS bundle many changes, and releases with OEL happening step with releases to Ory Network which are generally online.
While adding concurrent index creation will solve write locks, it may cause other issues with index hints afaik.
Preflight checklist
Ory Network Project
No response
Describe your problem
During one of our deployments, we noticed that the hydra db migration 'CREATE INDEX' step took too long while holding a write lock to the database. Since this is a database serving live traffic, we cannot afford to have a long down time.
Describe your ideal solution
Can we consider adding
CONCURRENTLY
to the CREATE INDEX sql statements, so that the db can still function while creating the indexes?Workarounds or alternatives
We considered running hydra janitor commands regularly, but it didn't help much and we also really want to have near zero down time.
Version
master
Additional Context
No response
The text was updated successfully, but these errors were encountered: