Git MultiSite for Gerrit Release Notes

WANdisco Git MultiSite for Gerrit Release: 1.0.2 (Build: g7f1bad3)

Date: February 5th, 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.

Gerrit:

• 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:

• 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.

You should contact WANdisco's support team for assistance if you encounter anything that appears to break any of these assumptions.

Available Packages

gerrit-install.tar.gz

- Installer

System Requirements

Before you install this software you must ensure that you currently meet the necessary system, software and hardware requirements for running WANdisco SVN MultiSite Plus:
docs.wandisco.com/git/ms/1.5/install.html#gerrit-checklist

Installation

You can find detailed instructions on how to get up and running in our online Git MultiSite User Guide:
docs.wandisco.com/git/gerrit/gerrit_install.html

Upgrades from an earlier version

Upgrades are not yet supported in this product.

Previous Release Notes

There are no previous releases for this product.

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.
  
  symptom:
  
  • 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.
  Fix:
  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.