|author||Antonio Barone <firstname.lastname@example.org>||Tue Apr 13 23:42:56 2021 +0200|
|committer||David Ostrovsky <email@example.com>||Tue Apr 13 23:43:30 2021 +0200|
Merge branch 'stable-3.3' * stable-3.3: AbstractSubcriber: Fix FloggerFormatString pattern flagged by error prone Rollback ref update when global-refdb update failure Allow gcloud-pubsub-events to be configured as events-broker Move ForwarderIndexProjectHandler to use common retry logic Move ForwarderIndexChangeHandler to use common retry logic Introduce common index with retries and move group handler Test cache invalidation behaviour inside a Gerrit daemon Honour index retries when indexing groups Enable SSL when starting kinesis locally Point to the correct kinesis-events artifact Disable AWS command line pager Add newline at EOF as required by HAProxy Allow kinesis-events to be configured as events-broker Rename GsonParser to CacheKeyJsonParser e2e-tests: Reuse the now available numberKey from GerritSimulation Delegate canPerformGC functionality to the wrapped instance Align testcontainers with v1.15 in Gerrit Change-Id: If6ec737e145489f2f471b71147f604353b220a22
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
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.