commit | 55e2ef1690661aa4c0e1c609e60cee07d0ea782b | [log] [tgz] |
---|---|---|
author | David Åkerman <davidak@axis.com> | Mon May 13 16:15:35 2024 +0200 |
committer | David Åkerman <davidak@axis.com> | Mon May 13 16:42:50 2024 +0200 |
tree | 6491fc419dcbba25239a21478c1ae468162366d1 | |
parent | 0e4b0342e50fd6e62df4b914e0ec8ec7a95bb9d0 [diff] |
Make events-rabbitmq manually ack messages after they are consumed To avoid losing messages that has been taken from the queue but not consummed by consumers during a restart of Gerrit. Change-Id: I4397a04fc7971a4b8e60f8c6cc7eec3de630ccfd
Publish gerrit stream events to a RabbitMQ queue. This plugin works with any version of Gerrit starting from v2.8. This plugin also implements most of the events-broker API, so RabbitMQ can be used as a message-broker in a multi-master setup. The one part that is missing is the implementation of the replayAllEvents method. However, this method is not needed by the multi-site plugin.
linux
java-1.8
Bazel
[amqp] uri = amqp://localhost [exchange] name = exchange-for-gerrit-queue [message] routingKey = com.foobar.www.gerrit [gerrit] name = foobar-gerrit hostname = www.foobar.com
3.14 (Freezed)
stable-2.10
master
is permanently latest but would not be updated by author anymore.3.1
3.0
2.0
1.4
1.3
1.2
1.1
monitor.failureCount
1.0
The Apache Software License, Version 2.0
Copyright (c) 2013 rinrinne a.k.a. rin_ne