system-config/playbooks/roles/gerrit
Clark Boylan 275fcba2e5 Explicitly disable Gerrit tracing.performanceLogging
According to the docs [0] this shouldn't be necessary as performance
logging only happens if a performance tracing plugin is installed.
However according to this repo discuss thread [1] there is always a
dummy performanceLogging instance installed. This same thread identifies
this as a likely source for large increase in memory utilization by
Gerrit when upgrading to 3.5.

Let's explicitly disable this tracing due to the memory overhead in prep
for our 3.5 upgrade. We can always flip the setting if we install a
performance tracing plugin in our Gerrit.

[0] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#tracing
[1] https://groups.google.com/g/repo-discuss/c/QUD7_LsEVks/m/kBDEeam4AgAJ

Change-Id: Iff438695aa6488fb5886120121946494b1edf003
2022-04-29 12:02:17 -07:00
..
defaults Upgrade Gerrit to 3.4 2022-01-24 10:54:54 -08:00
files Merge "Clean up Gerrit image builds" 2022-03-16 20:19:20 +00:00
handlers Add Apache to Ansible for Gerrit 2020-02-03 07:57:36 -06:00
tasks Use Gitea for Gerrit's code browser URLs 2022-02-18 18:50:00 +00:00
templates Explicitly disable Gerrit tracing.performanceLogging 2022-04-29 12:02:17 -07:00
README.rst Remove the mysql support from our gerrit role and image 2021-08-10 13:06:54 -07:00

README.rst

Run Gerrit.

This role assumes it will have a local MariaDB running adjacent to the Gerrit service. Variables below configure MariaDB connection details.

Role Variables