This patch refactors publishers by separating responsibilities and
introducing senders and waiters within publishers.
Change-Id: I90df59d61af2b40b516a5151c67c184fcc91e366
Co-Authored-By: Oleksii Zamiatin <ozamiatin@mirantis.com>
It was never clear was the purpose of this option.
For the RPC API point of view raising MessageDeliveryFailure is kind
of unexpected. For the Notification API, this is weird that when
application put retry=-1, the lib stop to retry only with rabbit.
So this change deprecates this option for removal.
Change-Id: I4ac3a062426418276c96e1745d1c96a8525c36da
By default oslo.cfg sets the default value as None. There is no
need to explicitly do this.
TrivialFix
Change-Id: I57fa9651ea56a180a910d6cbf7b7f385da8af239
This patch fixes the problem of sending messages in the following
configuration: use_router_proxy=True and use_pub_sub=False. Right
now we have incorrect both cast and fanout messages: cast acts as
fanout (instead of round-robin) and fanout duplicate each message
twice.
Change-Id: I2b039aa462ddde300fd50b3754e4fe66abf6e635
The Cyrus SASL library can only be initialized once per process. And
the configuration must remain available until all the tests have run.
Change-Id: I2810ecf53956fc5d4fcdc944f8e06237ca985e6a
Closes-Bug: #1591211
Each service being stopped should become
invisible for clients. For zmq listener that
means to cleanup it's redis target record
and stop updating it.
Starting of all consumers happen in init method.
Change-Id: Icd2d2fc73871de1d4845280432f5dec9eab8d381
Closes-Bug: #1590000
This patch proposes to allow TransportURLs to have query parameters
with driver-specific options which may override corresponding
values from a static configuration. As an example, the patch
implements this possibility in the pika driver. If the idea is
approved, it will be possible to also implement it in the other
drivers.
Change-Id: Ibb7e13b4509fde035a3c334cde9bc4c498f92140
* Connect endpoints to a newcomer router-proxy.
* Add TTL expriation to all redis keys.
* Update redis periodically from routers.
Change-Id: I0f73cc47f32f95bd4bb7e7f144adba491e94a346
It would be better if we could log a client port and some additional
information about a connection, to understand where is problems occurs.
The client port especially helpful for associating events in a rabbitmq.log
with oslo.messaging logs.
Change-Id: I0dae619f5a1688fb2f64fd90623fde2444609f04
There is a redundant for in help info of
default_notification_exchange, delete it.
Change-Id: I258bfe7fbc06f45398f0800ac69159dc313f2ff2
Closes-Bug: #1589381
