Move store related metrics to ChronicleMapStore

Do not emit all metrics from the chronicle-map cache implementation, but
rather split them so that the cache only emits cache-related metrics,
whilst the store emits storage-related ones.

This unlocks the possibility to centralize the emission of
store-related metrics regardless whether the store is accessed from
the ChronicleMapCacheImpl or the ChronicleMapCacheLoader.

Change-Id: Ie5e50a79f48f6e1e1ae4845b899bd9ad52e4c638
3 files changed
tree: 4cd75dfc7f9cd9bfac2cdb696d09f235a63414b4
  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.