commit | 8de36ada0c0bf967bb3a79a74f51ca0e414864a0 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Dec 30 22:06:48 2021 +0000 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Dec 30 22:25:52 2021 +0000 |
tree | d3fbed8bf707316a7badca9798cdb5897855c0f6 | |
parent | 782f8ba624b03fb0ee00dac43e9bde54d89442e3 [diff] |
Inject ProjectVersionRefUpdate as Provider<> The ProjectVersionRefUpdate relies on the injection of the GerritInstanceId which could be delayed in the bootstrap of Gerrit injectors chain at startup. Starting from v3.5, the GerritInstanceId, an optional injection, could still be null when the ReplicationStatus instance is created causing a Guice instantiation failure. Using a Provider<> resolves the issue and allows the resolution of the GerritInstanceId at runtime when all the Guice modules are instantiated. This change is applied in stable-3.3 for minimizing the conflicts of the merges up to master, as it is compatible with all branches even if not necessarily needed on stable-3.{3,4}. Change-Id: I638988205a004733e6531e6ac4126e2ba652ac06
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.
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.