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
97ebfd16
Commit
97ebfd16
authored
Nov 05, 2021
by
Mike Lockhart
Committed by
Amy Qualls
Nov 05, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Advise explicit UID/GID for multi-node Sidekiq
parent
b51ca778
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
0 deletions
+14
-0
doc/administration/sidekiq.md
doc/administration/sidekiq.md
+14
-0
No files found.
doc/administration/sidekiq.md
View file @
97ebfd16
...
...
@@ -74,6 +74,20 @@ you want using steps 1 and 2 from the GitLab downloads page.
postgresql
[
'trust_auth_cidr_addresses'
]
=
%w(127.0.0.1/32 10.10.1.30/32 10.10.1.31/32 10.10.1.32/32 10.10.1.33/32 10.10.1.38/32)
```
1.
If you run multiple Sidekiq nodes with a shared file storage, such as NFS, you must
specify the UIDs and GIDs to ensure they match between servers. Specifying the UIDs
and GIDs prevents permissions issues in the file system. This advice is similar to the
[
advice for Geo setups
](
geo/replication/multiple_servers.md#step-4-configure-the-frontend-application-nodes-on-the-geo-secondary-site
)
:
```
ruby
user
[
'uid'
]
=
9000
user
[
'gid'
]
=
9000
web_server
[
'uid'
]
=
9001
web_server
[
'gid'
]
=
9001
registry
[
'uid'
]
=
9002
registry
[
'gid'
]
=
9002
```
1.
Disable other services:
```
ruby
...
...
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