| commit | 23941d398dbc2d5411990b3205c821dfc9950196 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Mon Jul 19 23:10:13 2021 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed Jul 21 20:11:11 2021 +0100 |
| tree | 1f73b1225f70c4dba394b832dc9b03368d2e835d | |
| parent | ae297aa92c0436b746bc4fd38f835161eb49c93d [diff] |
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
Non-blocking and super-fast on-disk cache libModule for Gerrit Code Review based on ChronicleMap on-disk implementation.
This libModule is built like a Gerrit in-tree plugin, using Bazelisk. See the build instructions for more details.
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.
You can check how to migrate from H2 to chronicle-map here.