diff options
| author | Mehdi Abaakouk <sileht@redhat.com> | 2016-06-29 16:22:11 +0200 |
|---|---|---|
| committer | Mehdi Abaakouk <sileht@redhat.com> | 2016-06-29 16:26:25 +0200 |
| commit | 861a3aceb20dc148b65620c771eff978440a60e9 (patch) | |
| tree | 2504702e80c5d5eb1512965efa76035cd64193a2 | |
| parent | 5dfb1d8ef9c1f42e209227d0837fef74283f9d15 (diff) | |
| download | oslo-messaging-861a3aceb20dc148b65620c771eff978440a60e9.tar.gz | |
Remove rabbitmq max_retries
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
| -rw-r--r-- | oslo_messaging/_drivers/impl_rabbit.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/oslo_messaging/_drivers/impl_rabbit.py b/oslo_messaging/_drivers/impl_rabbit.py index d356938..f788bba 100644 --- a/oslo_messaging/_drivers/impl_rabbit.py +++ b/oslo_messaging/_drivers/impl_rabbit.py @@ -156,6 +156,7 @@ rabbit_opts = [ 'Default is 30 seconds.'), cfg.IntOpt('rabbit_max_retries', default=0, + deprecated_for_removal=True, deprecated_group='DEFAULT', help='Maximum number of RabbitMQ connection retries. ' 'Default is 0 (infinite retry count).'), |