| commit | b987059fc495f838a252bf276ae39fcbf0895c02 | [log] [tgz] |
|---|---|---|
| author | Saša Živkov <sasa.zivkov@sap.com> | Thu Jan 18 14:36:40 2024 +0100 |
| committer | Saša Živkov <sasa.zivkov@sap.com> | Thu Jan 18 14:36:40 2024 +0100 |
| tree | 65252fe373099aa21ebae3c57e88fe0aa5659f48 | |
| parent | f1933ae0642cda5f86b6bfff4cb7ecd54e523500 [diff] |
Use Duration instead of int for HEARTBEAT_INTERVAL The HEARTBEAT_INTERVAL was an int with the implicit unit of seconds. Duration is an amount of time that can be accessed using any time unit as needed by the caller. Change-Id: I40efed491004cd2d2e275bf0fe5dc2443b7d3d3a
This plugin provides an implementation of the Gerrit global refdb backed by Cloud Spanner.
Requirements for using this plugin are:
A global refdb implementation is a requirement for a Gerrit multi-master scenario in a multi-site setup to ensure refs are updated consistently across multiple Gerrit primary sites.
Refer to the Gerrit multi-site plugin for more details on the high level architecture.
The in-memory Cloud Spanner emulator can be used during development. There are several limitations of the emulator that differ from the production service.
An easy way to run the emulator is to use gcloud CLI and Docker. Following the install instructions here will provide a local instance that the plugin can access. The gcloud CLI commands will be sent to the emulator instead of the production service. A test spanner instance and database will need to be created.
gcloud spanner instances create test-instance --config=emulator-config --description="Test Instance" --nodes=1 gcloud spanner databases create global-refdb --instance=test-instance
There are several limitations of the emulator which differ from the production service.
In order to easily set up and begin testing the @PLUGIN@ plugin, the multi-site plugin's local environment setup can be used.
This simulates a multi-site setup using two local gerrit instances. Build the release.war to include @PLUGIN@ and follow the linked example setup.
Configuration details can be found in the @PLUGIN@ config documentation.
When not used with the emulator, the plugin requires the path to credentials in the config to authenticate with google. To create the key see the official documentation.