Autocommit action=MODIFY on file=Follow the RabbitMQ - Plan.md detected

Follow the RabbitMQ - Plan.md

@@ -1,4 +1,3 @@
-
 > What kind of issues we faced with rabbit
 > Is it a RabbitMQ setup issue or an Openstack issue ?
 
@@ -9,7 +8,6 @@
         * pause-minority helped crash the cluster
     * reset cluster was ... the solution
 
-
 > Which methods did we use to troubleshoot those issues
 > Observability, tools
 
@@ -28,14 +26,13 @@
                 * fanout mechanism 1 message published, duplicated to N queues
         * Nova rpc usage is clearly != neutron
 
-
 > Before going further, let's take some time to understand how oslo.messaging work
 > How RPC is implemented in Openstack
 
 * Under the hood ?
     * pub/sub mechanism
         * subscriber: RPC server topic=name
-            * setup class endpoints 
+            * setup class endpoints
             * create queues / setup consumer thread
         * publish with rpc provided methods
             * call - reply (topic / transient for reply)
@@ -43,10 +40,9 @@
             * cast / fanout=true (fanout queue)
     * notifications for external use: kafka
 
-
 > What we did to put rabbits back to their holes
 
-* Journey to get a stable infra. 
+* Journey to get a stable infra.
     * Infra
         * split rabbit-neutron / rabbit-\*
         * scale problematic clusters to 5 node
@@ -58,8 +54,8 @@
         * heartbeat in pthread fix
         * move from HA queue > Quorum queues
             * fix to autodelete broken quorum queues
-        * replace 'fanout' queues by stream queues 
-            *  reduce queue nb a lot 
-            * patch to avoid tcp reconnection when a queue is deleted (kombu/oslo) 
+        * replace 'fanout' queues by stream queues
+            * reduce queue nb a lot
+            * patch to avoid tcp reconnection when a queue is deleted (kombu/oslo)
         * reduce queues declared by a RPC server (3 queues by default to only 1)
         * use same connection for mutiple topics