Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
6036f162
Commit
6036f162
authored
Mar 21, 2017
by
Gabriel Mazetto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improvements to the upgrading instructions
parent
8a5fa5cc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
11 deletions
+11
-11
doc/gitlab-geo/updating_the_geo_nodes.md
doc/gitlab-geo/updating_the_geo_nodes.md
+11
-11
No files found.
doc/gitlab-geo/updating_the_geo_nodes.md
View file @
6036f162
...
...
@@ -25,22 +25,21 @@ For installations from source, [follow the instructions for your GitLab version]
# Upgrade to 9.0.x
> **IMPORTANT**: 9.0 requires manual steps in the secondary node,
> **IMPORTANT**: 9.0 requires manual steps in the secondary node
s
,
because we are upgrading PostgreSQL to 9.6 on the primary and Postgres
doesn't support upgrading secondary nodes while keeping the
Streaming Replication working.
Before starting the upgrade to 9.0 on both
**primary**
and
**secondary**
nodes,
stop all service in
the secondary node:
`gitlab-ctl stop`
and make a backup of the
`recovery.conf`
located at:
`/var/opt/gitlab/postgresql/data/recovery.conf`
stop all service in
each secondary nodes:
`gitlab-ctl stop`
and make a backup of
the
`recovery.conf`
located at:
`/var/opt/gitlab/postgresql/data/recovery.conf`
Follow regular upgrade instruction for 9.0 on the primary node.
At the end of the upgrade procedures your primary node will be running with
PostgreSQL on 9.6.x branch. To prevent a desynchronization of the repository
replication, stop all services but the
`postgresql`
as we will use it to
re-initialize the secondary node's database:
replication, follow these steps to stop all services but the
`postgresql`
as
we will use it to re-initialize the secondary node's database:
**Run in the primary node:**
...
...
@@ -57,19 +56,20 @@ to Create the `replica.sh` script and execute the instructions below:
```
gitlab-ctl stop
sudo cp /var/opt/gitlab/postgresql/data/recovery.conf ~/
# backup the recovery.conf from postgresql to preserv credentials
sudo cp /var/opt/gitlab/postgresql/data/recovery.conf /var/opt/gitlab
# prevent running database migrations on the secondary node:
touch /etc/gitlab/skip-automigrations
touch /etc/gitlab/skip-auto
-
migrations
#
we need to remov
e the old database:
rm -rf /var/opt/gitlab/postgresql
#
let's disabl
e the old database:
mv /var/opt/gitlab/postgresql{,.bak}
gitlab-ctl reconfigure
gitlab-ctl pg-upgrade
# see the stored credentials for the database, that you will need to re-initialize replication:
grep -s primary_conninfo
~
/recovery.conf
grep -s primary_conninfo
/var/opt/gitlab
/recovery.conf
# run the recovery script with the credentials above
bash /tmp/replica.sh
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment