diff options
| author | Evan Read <eread@gitlab.com> | 2019-06-21 09:19:57 +1000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-06-21 09:22:40 +1000 |
| commit | 635e2022603e082405e439b0037835514ddb9d34 (patch) | |
| tree | f5995adae391dbc0d10b6a8b4b7fc4dab92185fe | |
| parent | f1bbe60af2725a83a9b7975bc9f672894dc3b9d0 (diff) | |
| download | gitlab-ce-docs/add-another-fdw-troubleshoot-item.tar.gz | |
Review feedback implementeddocs/add-another-fdw-troubleshoot-item
| -rw-r--r-- | doc/administration/geo/replication/troubleshooting.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index f8469a158ad..846afd8f5f4 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -3,7 +3,7 @@ Setting up Geo requires careful attention to details and sometimes it's easy to miss a step. -Here is a list of steps you should take to attempt to fix problem +Here is a list of steps you should take to attempt to fix problem: - Perform [basic troubleshooting](#basic-troubleshooting). - Fix any [replication errors](#fixing-replication-errors). @@ -127,7 +127,7 @@ sudo gitlab-rails runner "puts Gitlab::Geo.current_node.inspect" and expect something like: -```text +```ruby #<GeoNode id: 2, schema: "https", host: "gitlab.example.com", port: 443, relative_url_root: "", primary: false, ...> ``` @@ -490,7 +490,9 @@ reload of the FDW schema. To manually reload the FDW schema: ### "Geo database has an outdated FDW remote schema" error -GitLab can error with the following message: +GitLab can error with a `Geo database has an outdated FDW remote schema` message. + +For example: ```text Geo database has an outdated FDW remote schema. It contains 229 of 236 expected tables. Please refer to Geo Troubleshooting. |