{"push_id":884032267,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b113dd65675f935ca17f84c96fe7f421b1f9982f","before":"7c840fc6b4a0e47c637be0796e99ffd9b15aba03","commits":[{"sha":"b113dd65675f935ca17f84c96fe7f421b1f9982f","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Updated openstack/openstack\nProject: openstack/oslo.messaging  19196fd20fd8e0468ef8a99b36e217710be68cac\n\nUse round robin failover strategy for Kombu driver\n\nShuffle strategy we use right now leads to increased reconnection time\nand provides no benefit. Sometimes it might lead to RPC operations\ntimeout because the strategy provides no guarantee on how long the\nreconnection process will take. See the referenced bug for details.\n\nOn the other side, round-robin strategy provides least achievable\nreconnection time. It also provides guarantee that if K of N RabbitMQ\nhosts are alive, it will take at most N - K + 1 attempts to\nsuccessfully reconnect to RabbitMQ cluster.\n\nWith shuffle strategy during failover clients connect to random hosts\nand so the load is distributed evenly between alive RabbitMQs.\nBut since we shuffle list of hosts before providing it to Kombu, load\nwill be distributed evenly with round-robin strategy as well.\n\nDocImpact\nA new configuration option kombu_failover_strategy for Kombu driver is\nadded. It determines how the next RabbitMQ node is chosen in case the\none we are currently connected to becomes unavailable. It takes effect\nonly if more than one RabbitMQ node is provided in config. Available\noptions are:\n\n * round-robin: each RabbitMQ host in the list is tried in cycle until\n   oslo.messaging successfully connects. Since oslo.messaging\n   shuffles list of RabbitMQ hosts, the order of hosts in the cycle\n   will be random and will not depend on order provided in config.\n\n * shuffle: oslo.messaging selects a random host from the list and\n   tries to connect to it. If connection fails, oslo.messaging repeats\n   attempt to connect to another random host. Oslo.messaging stops\n   once it successfully connects to a host. Note that in each\n   iteration a host to connect is selected independently of previous\n   iterations, i.e. it might happen that oslo.messaging will try to\n   connect to the same host several times in a row.\n\nThe option's default value is round-robin. Before the option was\nintroduced, the default strategy was shuffle. For the reasoning,\nsee the main body of the commit message and the referenced bug.\n\nCloses-Bug: #1519851\nChange-Id: I9a510c86bd5a6ce8b707734385af1a83de82804e","distinct":true,"url":"https://api.github.com/repos/openstack/openstack/commits/b113dd65675f935ca17f84c96fe7f421b1f9982f"}]}