Fix shutdown of consumers, NatsBrokerApi and the NATS connection

Do the shutdown in the following steps to implement graceful shutdown:
- drain connection, this drains all consumers stopping incoming
- disconnect the broker API, unsubscribing consumers and stopping
- close the connection
3 files changed
tree: 2bb8a0b32ebce3cac6b3aa1891dbc40e27ba5be0
  1. src/
  2. .gitignore
  3. BUILD
  4. external_plugin_deps.bzl
  5. Jenkinsfile

events-nats: Gerrit event producer for NATS

Build Status


This plugins allows to define a distributed stream of events published by Gerrit.

Events can be anything, from the traditional stream events to the Gerrit metrics.

This plugin requires Gerrit 3.6 or later.


  • linux
  • java-11
  • Bazel


events-nats plugin can be build as a regular ‘in-tree’ plugin. That means that is required to clone a Gerrit source tree first and then to have the events-nats plugin source directory into the /plugins path. Additionally, the plugins/external_plugin_deps.bzl file needs to be updated to match the events-nats plugin one.

git clone --recursive
git clone gerrit/plugins/events-nats
cd gerrit
rm plugins/external_plugin_deps.bzl
ln -s ./events-nats/external_plugin_deps.bzl plugins/.

To build the events-nats plugins, issue the command from the Gerrit source path:

bazel build plugins/events-nats

The output is created in


Minimum Configuration

Assuming a running NATS JetStream broker on the same Gerrit host, add the following settings to gerrit.config:

    [plugin "events-nats"]
        server = nats://localhost:4222


Starting a local NATS JetStream server for testing:

    docker run -d --name nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats -js

You can use the NATS command line client to inspect and manage NATS.