framework icon indicating copy to clipboard operation
framework copied to clipboard

Update RabbitMQ

Open wimpers opened this issue 8 years ago • 6 comments

Note: release 3.5.8 marks the final patch in the 3.5.x series. RabbitMQ 3.5.x is no longer maintained. Upgrade, and refer to the current version of RabbitMQ instead.

Since the 3.5.x release is no longer maintained it might be advised to

  • Go to Rabbitmq 3.6.x
  • Find something else

wimpers avatar Mar 03 '17 15:03 wimpers

If there is a reason to go for something else, please link the relevant tickets in GH

wimpers avatar Mar 03 '17 15:03 wimpers

Ubuntu 16.04 only ships 3.5.7-1. Do you want us to manually maintain a set of packages fetched from other sources?

khenderick avatar Mar 03 '17 15:03 khenderick

@saelbrec points out that setting up 3 RabbitMQs isn't ideal. (I believe @kinvaris did some research about that)

The BAM isn't favor of maintaining our own set of packages or changing to something else .

Maybe we should start listing the issues OPS/ framework has with the current version of RabbitMQ. ( @khenderick @jeroenmaelbrancke @jtorreke @matthiasdeblock )

wimpers avatar Mar 08 '17 16:03 wimpers

There is #860 which was moved to internal openvstorage/org_quality#33 There was also this pre GitHub era ticket OVS-4469

khenderick avatar Mar 09 '17 07:03 khenderick

@wimpers a few months ago we did some testing with a 3 node master setup. Here we saw that when shutting down 1 node the whole rabbitMQ cluster went down. Then I did some research about this and some forums pointed out you should at least have 4 nodes.

But a week ago we did some testing with 3 master nodes and the rabbitMQ cluster kept on going.

Although observing these results, I think it is recommended to have at least 4 nodes.

kinvaris avatar Mar 09 '17 10:03 kinvaris

Tested version: rabbitmq-server: 3.7.14-1

depends on: 20.x

Tested on 3N develop cluster.

Update:

ovs stop framework all

sudo apt-key adv --keyserver "hkps.pool.sks-keyservers.net" --recv-keys "0x6B73A36E6026DFCA"
wget -O - "https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc" | sudo apt-key add -
sudo apt-get install apt-transport-https
echo "deb https://dl.bintray.com/rabbitmq/debian xenial erlang-20.x" > /etc/apt/sources.list.d/bintray.erlang.list
echo "deb https://dl.bintray.com/rabbitmq/debian xenial main" > /etc/apt/sources.list.d/bintray.rabbitmq.list # fix rabbitmq version instead of main here
apt-get update
sudo apt-get install erlang-nox
sudo apt-get install rabbitmq-server

ovs start framework all

So i updated all nodes at once. Rolling upgrade was not tested, as discussed with @jtorreke

Results

This works fine, fusemountpoint communication is still intact.

sjovdnbos avatar Mar 29 '19 14:03 sjovdnbos