-
Notifications
You must be signed in to change notification settings - Fork 924
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
Stop pods downloading the DB on startup #15878
Comments
So, we could "just" delete this line from run-prod.sh: Line 10 in 25ff14b
Which would then let run-prod.sh just work without needing a fresh sqlite DB (remember that there's a recent copy of the DB baked into the Docker image) This would, however, mean that anything running sqlite as its DB would boot up with slightly stale data, potentially, which might cause us some surprises. Things to check that might misbehave if the sqlite DB isn't totally brand new:
Alternatively, we could make the inclusion of |
Also, in the k8s deployment, we call One flexible option (with an eye on demo servers and www-sitemap-generator) is to skip the download only if postgres is in use (so we can do a similar this to here where we check for sqlite being in use): Lines 160 to 172 in 25ff14b
|
cc @pmac for thoughts |
At the moment, when Bedrock starts, we have to run the init container which will download the sqlite DB as well as the l10n files, even though only the l10n files are needed.
If we turn off downloading the DB, the deployment fails.
It looks like we need to remove the check for the sentinel file that shows the DB has been downloaded
The text was updated successfully, but these errors were encountered: