diff options
| author | Luca Milanesio <luca.milanesio@gmail.com> | 2020-04-23 15:26:58 +0000 |
|---|---|---|
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2020-04-23 15:26:58 +0000 |
| commit | 7649b84b5204364123d0a953e269e68e9c8aef29 (patch) | |
| tree | b6f9934e2f5c4c5b21a0a7adb3172f1c5f4ceaa6 | |
| parent | e0a5b6c5474a7f6af2ace350e16b9adad85c9224 (diff) | |
| parent | 7b7c48059b78b7964b0772b42663de28c627401d (diff) | |
Merge "Clarify the limitations of gerrit+ssh in replication.config" into stable-2.16v2.16.18
| -rw-r--r-- | src/main/resources/Documentation/config.md | 28 |
1 files changed, 22 insertions, 6 deletions
diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md index c9356b0..1309aeb 100644 --- a/src/main/resources/Documentation/config.md +++ b/src/main/resources/Documentation/config.md @@ -177,17 +177,33 @@ remote.NAME.adminUrl local environment. In that case, an alternative SSH url could be specified to repository creation. - To enable replication to different Gerrit instance use `gerrit+ssh://` + *Backward compatibility notice* + + Before Gerrit v2.13 it was possible to enable replication to different + Gerrit masters using `gerrit+ssh://` as protocol name followed by hostname of another Gerrit server eg. `gerrit+ssh://replica1.my.org/` - In this case replication will use Gerrit's SSH API to - create/remove projects and update repository HEAD references. - - NOTE: In order to replicate project deletion, the + In that case replication would have used Gerrit's SSH API to + create/remove projects and update repository HEAD references + and, in order to replicate project deletion, the link:https://gerrit-review.googlesource.com/admin/projects/plugins/delete-project delete-project[delete-project] - plugin must be installed on the other Gerrit. + plugin was needed to be installed on the other Gerrit. + + The `gerrit+ssh` option is kept for backward compatibility, however + the use-case behind it is not valid anymore since the introduction of + Lucene indexes and the removal of ReviewDb, which would require + a lot more machinery to setup a master to master replication scenario. + + The `gerrit+ssh` option is still possible but is limited to the + ability to replicate only regular Git repositories that do not + contain any code-review or NoteDb information. + + Using `gerrit+ssh` for replicating all Gerrit repositories + would result in failures on the All-Users.git replication and + would not be able to replicate changes magic refs and indexes + across nodes. remote.NAME.receivepack : Path of the `git-receive-pack` executable on the remote |