Use existing pre-configured cache config for H2 migration

When migrating from H2 to ChronicleMap, it may be useful
to pre-define the target cache configuration beforehand.
That allows the Gerrit admin to correctly tune a desired
set of parameters and use them during the cutover from H2
to ChronicleMap.

Keep the default behaviour (auto-tune from H2) when the
average key and values sizes are not set, so to allow a
smooth migration for those Gerrit admins that do not
need to get the cutover fully automated.

Change-Id: I900cc0ed4a83fde6f77c13eb69c4212251834525
3 files changed
tree: 1f73b1225f70c4dba394b832dc9b03368d2e835d
  1. src/
  2. .gitignore
  3. BUILD
  4. external_plugin_deps.bzl
  5. Jenkinsfile

Persistent cache for Gerrit, based on ChronicleMap

Non-blocking and super-fast on-disk cache libModule for Gerrit Code Review based on ChronicleMap on-disk implementation.

How to build

This libModule is built like a Gerrit in-tree plugin, using Bazelisk. See the build instructions for more details.


  • Install cache-chronicalmap module

Install the chronicle-map module into the $GERRIT_SITE/lib directory.

Add the cache-chroniclemap module to $GERRIT_SITE/etc/gerrit.config as follows:

  installModule = com.googlesource.gerrit.modules.cache.chroniclemap.ChronicleMapCacheModule

For further information and supported options, refer to config documentation.

Migration from H2 caches

You can check how to migrate from H2 to chronicle-map here.