Navigation:  v | Release Notes | Integration | Install | Integration | Administration | Git MultiSite | Glossary |

Git MultiSite for Gerrit Release Notes

WANdisco Git MultiSite for Gerrit Release: 1.2.1, Build: 7a0685bf

May 12, 2015

New features

Introduced support for Percona XtraDB to allow master-master DB replication. See Percona XtraDB Installation Guide, Percona Database Configuration, and Migrating from MySQL to Percona XtraDB Cluster.

Fixed issues

Fixed an issue with event stream replication that caused Lucene Index events to be duplicated.

Known issues

Gerrit Cache Replication is not supported. As a result, it is recommended that caching is turned off so that Gerrit MS will query the database for the latest information.

WANdisco Git MultiSite for Gerrit Release: 1.2, Build: 5551e616

March 23, 2015

New features

  • Installer code has moved from its own gerrit-installer repository into the forked Gerrit repository.
  • The version format of Gerrit has been modified to reflect our changes.
  • The installer has been rewritten.
  • We have implemented Replicated Event Streams. For information about settings, see Configure for Gerrit event stream. US792

WANdisco Git MultiSite for Gerrit Release: 1.0.2, Build: g7f1bad3

February 5, 2015

Git MultiSite for Gerrit allows Gerrit to be integrated with WANdisco's Git MultiSite. This integration product operates under the following design assumptions.

  • All nodes run both Gerrit and Git MultiSite on the same machine under the same system account.
  • New repositories are created through Gerrit and all repositories are Gerrit-controlled.
  • Each node requires either a direct connection to the RDBMS or a pass-through read-only RDBMS mirror.
  • Gerrit's slave mode is not supported.
  • Gerrit event listeners and post-* hooks only fire on the node that receives the repository event. However, regular Git hooks work as expected, including replicated post-* hooks.
Git MultiSite:
  • GitMS does not manage (replicate) the Gerrit RDBMS.
  • Nodes must be one of the active types AVT/AV/A.
  • A single replication group is used for Gerrit. The concept of replication groups is not exposed through Gerrit's UI.

Contact WANdisco's support team if you see anything that seems to break any of these assumptions.

Available packages

- Installer

System requirements

Before you install this software, ensure that your deployment meets the necessary system, software, and hardware requirements for running WANdisco SVN MultiSite Plus:


For installation instructions see our online Git MultiSite User Guide:

Upgrades from an earlier version

Upgrades are not yet supported in this product.

Previous Release Notes

This document contains all release notes.

New features

  • We now implement version 2.9.4 of Gerrit.

Fixed issues

  • We've fixed an issue with the database connection pooling, which resulted in an abnormal consumption of connections. DE380

  • Fixed Gerrit indexing errors that occured when using a master-slave-slave configuration for MySQL proxy. GER-183, GER-184

Known issues

  • Lucene change index can lose sync between nodes
    We've seen rare instances where Gerrit's Lucene index has fallen out of sync between nodes, even after calls to reindex.

    • Details on the Gerrit UI such as status, timestamps etc differ between nodes.
    • Alternatively, a discrepancy can be seen between the index and a drill-down page which doesn't use the index and instead goes directly to the database.
    The loss of sync usually lasts only as long as a the next reindex event, however there may be situations where you need to ensure that content is consistent. For this you can run our reindexing script. See Forcing a reindex.

  • When installing GerritMS and running the installer.sh script, it can incorrectly fail to determine the database type in use. This is due to a case handling error when parsing the gerrit.config file. The script will require that the database.type value be in lowercase - so "mysql" instead of "MYSQL", for example. GER-206

  • Gerrit performance affected by non-local database
    The Gerrit web application relies on having a low latency connection to its database. If this requirement cannot be met - for example, for a Gerrit node in Europe communicating with a database in the US, the performance (and UI performance especially) will be poor on installations with a large number of changes. This is only avoidable by configuring Gerrit to use a Master-Slave database configuration with a write-through proxy.