diff options
| author | Marcel Amirault <ravlen@gmail.com> | 2019-06-05 03:29:33 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-06-05 03:29:33 +0000 |
| commit | 3c31d793c8321e7b02c36ea81c82ff63fed55d12 (patch) | |
| tree | 2a64d805d93c10e5c2ab8ddb5760304289cc6b28 /doc/administration/geo/disaster_recovery | |
| parent | ebc18b45c7e72b28c1981446c95433611903868d (diff) | |
| download | gitlab-ce-3c31d793c8321e7b02c36ea81c82ff63fed55d12.tar.gz | |
Docs: Update all links to relative in /workflow and /administration
Diffstat (limited to 'doc/administration/geo/disaster_recovery')
| -rw-r--r-- | doc/administration/geo/disaster_recovery/planned_failover.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md index 88ab12d910a..b8071b5993f 100644 --- a/doc/administration/geo/disaster_recovery/planned_failover.md +++ b/doc/administration/geo/disaster_recovery/planned_failover.md @@ -113,7 +113,7 @@ If any objects are failing to replicate, this should be investigated before scheduling the maintenance window. Following a planned failover, anything that failed to replicate will be **lost**. -You can use the [Geo status API](https://docs.gitlab.com/ee/api/geo_nodes.html#retrieve-project-sync-or-verification-failures-that-occurred-on-the-current-node) to review failed objects and +You can use the [Geo status API](../../../api/geo_nodes.md#retrieve-project-sync-or-verification-failures-that-occurred-on-the-current-node) to review failed objects and the reasons for failure. A common cause of replication failures is the data being missing on the |