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
33b6f6fd
Commit
33b6f6fd
authored
Jan 05, 2018
by
James Ramsay
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove duplicate manual NTP check
The NTP check is now included in `gitlab-rake gitlab:geo:check`
parent
1eed12ac
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
5 additions
and
46 deletions
+5
-46
changelogs/unreleased-ee/jramsay4480-remove-ntp-check-from-geo-docs.yml
...eleased-ee/jramsay4480-remove-ntp-check-from-geo-docs.yml
+5
-0
doc/gitlab-geo/database.md
doc/gitlab-geo/database.md
+0
-23
doc/gitlab-geo/database_source.md
doc/gitlab-geo/database_source.md
+0
-23
No files found.
changelogs/unreleased-ee/jramsay4480-remove-ntp-check-from-geo-docs.yml
0 → 100644
View file @
33b6f6fd
---
title
:
Remove unnecessary NTP checks now included in gitlab:geo:check
merge_request
:
3940
author
:
type
:
other
doc/gitlab-geo/database.md
View file @
33b6f6fd
...
...
@@ -242,23 +242,6 @@ The following guide assumes that:
will need it when setting up the secondary! The certificate is not sensitive
data.
1.
Verify that clock synchronization is enabled.
>**Important:**
For Geo to work correctly, all nodes must have their clocks
synchronized. It is not required for all nodes to be set to the same time
zone, but when the respective times are converted to UTC time, the clocks
must be synchronized to within 60 seconds of each other.
Verify NTP sync is enabled using:
```bash
timedatectl status | grep 'NTP synchronized'
```
Refer to your Linux distribution documentation to setup clock
synchronization. This can easily be done using any NTP-compatible daemon.
### Step 2. Add the secondary GitLab node
To prevent the secondary geo node from trying to act as the primary once the
...
...
@@ -371,12 +354,6 @@ because we have not yet configured the secondary server. This is the next step.
gitlab-ctl reconfigure
```
1.
Verify that clock synchronization is enabled, using:
```bash
timedatectl status | grep 'NTP synchronized'
```
1.
Verify the secondary if configured correctly and that the primary is
reachable:
...
...
doc/gitlab-geo/database_source.md
View file @
33b6f6fd
...
...
@@ -201,23 +201,6 @@ The following guide assumes that:
`netstat -plnt`
to make sure that PostgreSQL is listening to the server's
public IP.
1.
Verify that clock synchronization is enabled.
>**Important:**
For Geo to work correctly, all nodes must have their clocks
synchronized. It is not required for all nodes to be set to the same time
zone, but when the respective times are converted to UTC time, the clocks
must be synchronized to within 60 seconds of each other.
Verify NTP sync is enabled, using:
```bash
timedatectl status | grep 'NTP synchronized'
```
Refer to your Linux distribution documentation to setup clock
synchronization. This can easily be done using any NTP-compatible daemon.
### Step 2. Add the secondary GitLab node
Follow the steps in
[
"add the secondary GitLab node"
](
database.md#step-2-add-the-secondary-gitlab-node
)
.
...
...
@@ -243,12 +226,6 @@ the primary's database" step, continue here:
1.
Restart PostgreSQL for the changes to take effect.
1.
Verify that clock synchronization is enabled, using:
```bash
timedatectl status | grep 'NTP synchronized'
```
#### Enable tracking database on the secondary server
Geo secondary nodes use a tracking database to keep track of replication status
...
...
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