diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-04 00:07:52 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-04 00:07:52 +0000 |
commit | 4fe93274dec62ff7361a67be88e320131d66b788 (patch) | |
tree | 98ae79e3101ffd6569fc48bb4c7ad8808540ceb8 /doc/administration/geo/replication | |
parent | bbaf2bb0438b1c71020d9d216feb528add225a7f (diff) | |
download | gitlab-ce-4fe93274dec62ff7361a67be88e320131d66b788.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/geo/replication')
4 files changed, 29 insertions, 2 deletions
diff --git a/doc/administration/geo/replication/datatypes.md b/doc/administration/geo/replication/datatypes.md index 9ee215c60c5..feb0c2f2f4d 100644 --- a/doc/administration/geo/replication/datatypes.md +++ b/doc/administration/geo/replication/datatypes.md @@ -131,7 +131,7 @@ successfully, you must replicate their data using some other means. | Project wiki repository | **Yes** | **Yes** | | | Project designs repository | **Yes** | [No][design-verification] | | | Uploads | **Yes** | [No][upload-verification] | Verified only on transfer, or manually (*1*)| -| LFS objects | **Yes** | [No][lfs-verification] | Verified only on transfer, or manually (*1*)| +| LFS objects | **Yes** | [No][lfs-verification] | Verified only on transfer, or manually (*1*). Unavailable for new LFS objects in 11.11.x and 12.0.x (*2*). | | CI job artifacts (other than traces) | **Yes** | [No][artifact-verification] | Verified only manually (*1*) | | Archived traces | **Yes** | [No][artifact-verification] | Verified only on transfer, or manually (*1*)| | Personal snippets | **Yes** | **Yes** | | @@ -148,7 +148,10 @@ successfully, you must replicate their data using some other means. | Content in object storage | **Yes** | No | | - (*1*): The integrity can be verified manually using - [Integrity Check Rake Task](../../raketasks/check.md) on both nodes and comparing the output between them. + [Integrity Check Rake Task](../../raketasks/check.md) on both nodes and comparing + the output between them. +- (*2*): GitLab versions 11.11.x and 12.0.x are affected by [a bug that prevents any new + LFS objects from replicating](https://gitlab.com/gitlab-org/gitlab/issues/32696). [design-replication]: https://gitlab.com/groups/gitlab-org/-/epics/1633 [design-verification]: https://gitlab.com/gitlab-org/gitlab/issues/32467 diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index b5be29f7dff..c3e1da3311f 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -377,6 +377,14 @@ sudo gitlab-ctl reconfigure This will increase the timeout to three hours (10800 seconds). Choose a time long enough to accommodate a full clone of your largest repositories. +### New LFS objects are never replicated + +If new LFS objects are never replicated to secondary Geo nodes, check the version of +GitLab you are running. GitLab versions 11.11.x or 12.0.x are affected by +[a bug that results in new LFS objects not being replicated to Geo secondary nodes](https://gitlab.com/gitlab-org/gitlab/issues/32696). + +To resolve the issue, upgrade to GitLab 12.1 or newer. + ### Resetting Geo **secondary** node replication If you get a **secondary** node in a broken state and want to reset the replication state, diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md index d094ccf3e54..df66b1b36ec 100644 --- a/doc/administration/geo/replication/updating_the_geo_nodes.md +++ b/doc/administration/geo/replication/updating_the_geo_nodes.md @@ -14,6 +14,8 @@ different steps. - [Updating to GitLab 12.7](version_specific_updates.md#updating-to-gitlab-127) - [Updating to GitLab 12.2](version_specific_updates.md#updating-to-gitlab-122) - [Updating to GitLab 12.1](version_specific_updates.md#updating-to-gitlab-121) +- [Updating to GitLab 12.0](version_specific_updates.md#updating-to-gitlab-120) +- [Updating to GitLab 11.11](version_specific_updates.md#updating-to-gitlab-1111) - [Updating to GitLab 10.8](version_specific_updates.md#updating-to-gitlab-108) - [Updating to GitLab 10.6](version_specific_updates.md#updating-to-gitlab-106) - [Updating to GitLab 10.5](version_specific_updates.md#updating-to-gitlab-105) diff --git a/doc/administration/geo/replication/version_specific_updates.md b/doc/administration/geo/replication/version_specific_updates.md index 77fcaaba764..a697d07ded4 100644 --- a/doc/administration/geo/replication/version_specific_updates.md +++ b/doc/administration/geo/replication/version_specific_updates.md @@ -45,6 +45,20 @@ This can be temporarily disabled by running the following before updating: sudo touch /etc/gitlab/disable-postgresql-upgrade ``` +## Updating to GitLab 12.0 + +WARNING: **Warning:** +This version is affected by [a bug that results in new LFS objects not being replicated to +Geo secondary nodes](https://gitlab.com/gitlab-org/gitlab/issues/32696). The issue is fixed +in GitLab 12.1. Please upgrade to GitLab 12.1 or newer. + +## Updating to GitLab 11.11 + +WARNING: **Warning:** +This version is affected by [a bug that results in new LFS objects not being replicated to +Geo secondary nodes](https://gitlab.com/gitlab-org/gitlab/issues/32696). The issue is fixed +in GitLab 12.1. Please upgrade to GitLab 12.1 or newer. + ## Updating to GitLab 10.8 Before 10.8, broadcast messages would not propagate without flushing |