Skip to content
Snippets Groups Projects
Commit 07ee8224159a authored by Marcel Amirault's avatar Marcel Amirault
Browse files

Merge branch 'hchouraria-docs-omnibus-keep-auto-migrate-enabled-deploy-node' into 'master'

Clarify disabling DB migrations

See merge request gitlab-org/omnibus-gitlab!5680
No related branches found
No related tags found
2 merge requests!60Heptapod 0.28 is the new stable,!56Heptapod 0.28 / GitLab 14.5
......@@ -948,7 +948,7 @@
If you have multiple GitLab servers sharing a database, you will want to limit the
number of nodes that are performing the migration steps during reconfiguration.
Edit `/etc/gitlab/gitlab.rb`:
Edit `/etc/gitlab/gitlab.rb` to append:
```ruby
# Enable or disable automatic database migrations
......@@ -952,6 +952,7 @@
```ruby
# Enable or disable automatic database migrations
# on all hosts except the designated deploy node
gitlab_rails['auto_migrate'] = false
```
......@@ -955,9 +956,6 @@
gitlab_rails['auto_migrate'] = false
```
Don't forget to remove the `#` comment characters at the beginning of this
line.
`/etc/gitlab/gitlab.rb` should have file permissions `0600` because it contains
plain-text passwords.
......@@ -961,7 +959,9 @@
`/etc/gitlab/gitlab.rb` should have file permissions `0600` because it contains
plain-text passwords.
The next time a reconfigure is triggered, the migration steps will not be performed.
The next time hosts carrying the above configuration are reconfigured, the migration steps are not performed.
To avoid schema related post-upgrade errors, the host marked as [the deploy node](https://docs.gitlab.com/ee/update/zero_downtime.html#multi-node--ha-deployment) must have `gitlab_rails['auto_migrate'] = true` during upgrades.
### Setting client statement_timeout
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment