| tag | d132658abcb5ea208891f68d805c20eaacd4a416 | |
|---|---|---|
| tagger | Luca Milanesio <luca.milanesio@gmail.com> | Thu Aug 24 14:17:01 2023 +0100 |
| object | 3e834ac8cc8c702feae85b3cc39728fd4a4dd99a |
v3.5.6
| commit | 3e834ac8cc8c702feae85b3cc39728fd4a4dd99a | [log] [tgz] |
|---|---|---|
| author | Alvaro Vilaplana Garcia <alvaro.vilaplana@gmail.com> | Fri Aug 18 15:17:42 2023 +0100 |
| committer | Alvaro Vilaplana Garcia <alvaro.vilaplana@gmail.com> | Fri Aug 18 15:17:42 2023 +0100 |
| tree | 1380844572c9ab83a4fd5cbc8eb9f5cb274c276f | |
| parent | 6fe04c4cef19f7a1ff80a50c587a61f3fccb167e [diff] | |
| parent | 65387545a5a651e1f6b6ade83a28ef01dc5947dc [diff] |
Merge branch 'stable-3.4' into stable-3.5 * stable-3.4: Remove replication plugin link from local environment setup Remove replication plugin code/variables from local environment setup Fix local environment setup: replication miss-configuration Change-Id: I0ebf33f7b4ba0216f0e44d9e8fa7eed6618b8c6c
This plugin allows to deploy a distributed cluster of multiple Gerrit masters each using a separate site without sharing any storage. The alignment between the masters happens using the replication plugin and an external message broker.
Requirements for the Gerrit masters are:
NOTE: The multi-site plugin will not start if Gerrit is not yet migrated to NoteDb.
Supports multiple read/write masters across multiple sites across different geographic locations. The Gerrit nodes are kept synchronized between each other using the replication plugin and a global ref-database in order to detect and prevent split-brains.
For more details on the overall multi-site design and roadmap, please refer to the multi-site plugin DESIGN.md document
This plugin is released under the same Apache 2.0 license and copyright holders as of the Gerrit Code Review project.
The multi-site plugin can only be built in tree mode, by cloning Gerrit and the multi-site plugin code, and checking them out on the desired branch.
Example of cloning Gerrit and multi-site for a stable-2.16 build:
git clone -b stable-2.16 https://gerrit.googlesource.com/gerrit git clone -b stable-2.16 https://gerrit.googlesource.com/plugins/multi-site cd gerrit/plugins ln -s ../../multi-site . rm external_plugin_deps.bzl ln -s multi-site/external_plugin_deps.bzl .
Example of building the multi-site plugin:
cd gerrit bazel build plugins/multi-site
The multi-site.jar plugin is generated to bazel-bin/plugins/multi-site/multi-site.jar.
Example of testing the multi-site plugin:
cd gerrit bazel test plugins/multi-site:multi_site_tests
NOTE: The multi-site tests include also the use of Docker containers for instantiating and using a Kafka/Zookeeper broker. Make sure you have a Docker daemon running (/var/run/docker.sock accessible) or a DOCKER_HOST pointing to a Docker server.
Each Gerrit server of the cluster must be identified with a globally unique instance-id defined in $GERRIT_SITE/etc/gerrit.config. When migrating from a multi-site configuration with Gerrit v3.3 or earlier, you must reuse the instance-id value stored under $GERRIT_SITE/data/multi-site.
Example:
[gerrit] instanceId = 758fe5b7-1869-46e6-942a-3ae0ae7e3bd2
Install the multi-site plugin into the $GERRIT_SITE/lib directory of all the Gerrit servers that are part of the multi-site cluster. Create a symbolic link from $GERRIT_SITE/lib/multi-site.jar into the $GERRIT_SITE/plugins.
Add the multi-site module to $GERRIT_SITE/etc/gerrit.config as follows:
[gerrit] installDbModule = com.googlesource.gerrit.plugins.multisite.GitModule installModule = com.googlesource.gerrit.plugins.multisite.Module
For more details on the configuration settings, please refer to the multi-site configuration documentation.
You also need to setup the Git-level replication between nodes, for more details please refer to the replication plugin documentation.
For information about available HTTP endpoints please refer to the documentation.