From 95d04028747b1f335ef52d5b204f10e7a10ab023 Mon Sep 17 00:00:00 2001 From: Edu Alcaniz Date: Tue, 5 Jul 2016 12:34:03 +0200 Subject: [PATCH] Fix misstyping issue Change-Id: I5f6ed9e021c2f218046ea6fed55e58018b595392 --- oslo_messaging/_drivers/zmq_driver/broker/zmq_proxy.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/oslo_messaging/_drivers/zmq_driver/broker/zmq_proxy.py b/oslo_messaging/_drivers/zmq_driver/broker/zmq_proxy.py index 4ee368813..77a47d22f 100644 --- a/oslo_messaging/_drivers/zmq_driver/broker/zmq_proxy.py +++ b/oslo_messaging/_drivers/zmq_driver/broker/zmq_proxy.py @@ -48,7 +48,7 @@ class ZmqProxy(object): 2. Routers should be transparent for clients and servers. Which means it doesn't change the way of messaging between client and the final target by hiding the target from a client. - 3. Router may be restarted or get down at any time loosing all messages + 3. Router may be restarted or shut down at any time losing all messages in its queue. Smart retrying (based on acknowledgements from server side) and load balancing between other Router instances from the client side should handle the situation.