commit | 7d17062cfc27898f9d0fc6d1e3c323f19b2b5ee8 | [log] [tgz] |
---|---|---|
author | David Åkerman <davidak@axis.com> | Fri Feb 21 16:52:49 2025 +0100 |
committer | David Åkerman <davidak@axis.com> | Thu Aug 21 12:47:27 2025 +0200 |
tree | 38b54885e578cde2967f65b272ea1c2935dc85d8 | |
parent | 30ef8e2467aeaf9bd1f965e104436e0f97960ab1 [diff] |
Add support for RabbitMQ streams With streams you will be able to use the replay functionality. To keep track of the current message an offset is used. The offset is periodically saved/stored and when replayAll is called the consumer start to consume from the beginning of the stream. Every stream.windowSize we store (current offset - stream.windowSize) as the offset to make sure we replay missed messages when we restart a multi-site instance. Change-Id: I51a49533248ce94d1e6831071b033869c86db6d8
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