|author||Antonio Barone <firstname.lastname@example.org>||Tue Mar 23 21:13:38 2021 +0100|
|committer||Luca Milanesio <email@example.com>||Thu Apr 01 00:56:16 2021 +0000|
Honour index retries when indexing groups Similarly to the ForwardedIndexChangeHandler, the ForwardedGroupChangeHandler will attempt multiple reindexes up to `index.maxTries`, every `index.retryInterval` milliseconds. To be able to understand whether replication is completed and the local group ref is up-to-date, two main changes have been introduced: - A GroupChecker class, with the responsibility to lookup in All-Users for the status of a specified group - An extra field in the GroupIndexEvent class, to indicate which particular sha1 the ref group was updated to, so that GroupChecker could perform a specific lookup. Note that to maintain backward-compatibility with previous GroupIndexEvent's, the additional field was made optional, so that old events can still be de-serialized and consumed by this version of the multi-site code. Bug: Issue 14161 Change-Id: Ifc171a49a0c360ceb39538a6d133154fcd0050e9
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.
Currently, the only mode supported is one primary read/write master and multiple read-only masters but eventually the plan is to support multiple read/write masters. The read/write master is handling any traffic while the read-only masters are serving the Gerrit GUI assets, the HTTP GET REST API and git fetch requests (git-upload-pack). The read-only masters are kept synchronized with the read/write master in order to be always ready to become a read/write master.
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
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
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.