commit | 09fbfb9aea8059d3a04fdea74a7779f65924590f | [log] [tgz] |
---|---|---|
author | Rikard Almgren <rikardal@axis.com> | Fri Apr 12 12:04:36 2024 +0200 |
committer | Rikard Almgren <rikardal@axis.com> | Fri Apr 12 13:50:43 2024 +0200 |
tree | a0b5ac66dfb5c1f155bc6b691b6b8820ca82d056 | |
parent | 608f6e731e22babb0f9cbd7424c9b1d12bfb2e27 [diff] |
Only publish events generated by current Instance When in multi-primary setup the event stream contains events from all primaries, however each primary has an events-rabbitmq plugin and should only publish events that originates from that primary. Otherwise the events published to the exchange would be duplicated by nbr_of_primaries^2. Bug: Issue 333981067 Change-Id: I5e35605c61bb45079d96d94e7db3eb24c74cf464
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