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
163d2c4d
Commit
163d2c4d
authored
Nov 20, 2017
by
Chenjerai Katanda
Committed by
Marin Jankovski
Nov 20, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update docs to show use of high availability redis and sentinel roles
parent
b0aca019
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
10 deletions
+16
-10
doc/administration/high_availability/redis.md
doc/administration/high_availability/redis.md
+16
-10
No files found.
doc/administration/high_availability/redis.md
View file @
163d2c4d
...
...
@@ -268,10 +268,9 @@ The prerequisites for a HA Redis setup are the following:
1.
Edit
`/etc/gitlab/gitlab.rb`
and add the contents:
```ruby
# Enable the master role and disable all other services in the machine
# (you can still enable Sentinel).
redis_master_role['enable'] = true
# Specify server role as 'redis_master_role'
roles ['redis_master_role']
# IP address pointing to a local IP that the other machines can reach to.
# You can also set bind to '0.0.0.0' which listen in all interfaces.
# If you really need to bind to an external accessible IP, make
...
...
@@ -285,6 +284,7 @@ The prerequisites for a HA Redis setup are the following:
# Set up password authentication for Redis (use the same password in all nodes).
redis['password'] = 'redis-password-goes-here'
```
1.
Only the primary GitLab application server should handle migrations. To
prevent database migrations from running on upgrade, add the following
...
...
@@ -296,6 +296,10 @@ The prerequisites for a HA Redis setup are the following:
1.
[
Reconfigure Omnibus GitLab
][
reconfigure
]
for the changes to take effect.
> Note: You can specify multiple roles like sentinel and redis as:
> roles ['redis_sentinel_role', 'redis_master_role']. Read more about high
> availability roles at https://docs.gitlab.com/omnibus/roles/
### Step 2. Configuring the slave Redis instances
1.
SSH into the
**slave**
Redis server.
...
...
@@ -308,11 +312,9 @@ The prerequisites for a HA Redis setup are the following:
1.
Edit
`/etc/gitlab/gitlab.rb`
and add the contents:
```ruby
# Enable the slave role and disable all other services in the machine
# (you can still enable Sentinel). This will also set automatically
# `redis['master'] = false`.
redis_slave_role['enable'] = true
# Specify server role as 'redis_slave_role'
roles ['redis_slave_role']
# IP address pointing to a local IP that the other machines can reach to.
# You can also set bind to '0.0.0.0' which listen in all interfaces.
# If you really need to bind to an external accessible IP, make
...
...
@@ -345,6 +347,10 @@ The prerequisites for a HA Redis setup are the following:
1.
[
Reconfigure Omnibus GitLab
][
reconfigure
]
for the changes to take effect.
1.
Go through the steps again for all the other slave nodes.
> Note: You can specify multiple roles like sentinel and redis as:
> roles ['redis_sentinel_role', 'redis_slave_role']. Read more about high
> availability roles at https://docs.gitlab.com/omnibus/roles/
---
These values don't have to be changed again in
`/etc/gitlab/gitlab.rb`
after
...
...
@@ -392,7 +398,7 @@ multiple machines with the Sentinel daemon.
be duplicate below):
```ruby
r
edis_sentinel_role['enable'] = true
r
oles ['redis_sentinel_role']
# Must be the same in every sentinel node
redis['master_name'] = 'gitlab-redis'
...
...
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