Normalize chronicle-map configuration parameters

Chronicle-Map used to be instantiated not just for persistent caches,
but also for persistent caches that were effectively disabling
persistency by setting 'diskLimit' to zero or a negative value.

This, however was fixed in[1] and since then the memory cache factory is
used for those caches.

Chronicle-map should not be able to be instantiated without a specific
persisted file: for this reason, the persistedFile is now passed in
directly by the factory, so that chronicle-map just cannot be
instantiated without one.

Consequently, some parameters that were used before to check and
construct the file path, such as name, version and diskLimit have now
been removed.

[1]If911621de8ca9676d29850e449f14c684f73710e

Change-Id: I088be18d731371997f2af31ca3de8b80d36be18e
5 files changed
tree: 5a9d913afb22e8463dd13713a9328a3df33226e3
  1. src/
  2. .gitignore
  3. BUILD
  4. build.md
  5. config.md
  6. external_plugin_deps.bzl
  7. Jenkinsfile
  8. LICENSE
  9. metrics.md
  10. README.md
  11. tuning.md
README.md

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.

Setup

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

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

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