Skip to content

Instantly share code, notes, and snippets.

View michaelklishin's full-sized avatar

Michael Klishin michaelklishin

View GitHub Profile

How to set up a RabbitMQ package (apt) mirror

Below is a very brief version that demonstrates how a mirror of Team RabbitMQ's apt repository can be set up and hosted by anyone.

It assumes basic familiarity with Debian-based Linux and Nginx. There are only two tools involved:

  • apt-mirror to sync the repo (please sync from ppa1.novemberain.com which has a very ample traffic quota in comparison to our Cloudsmith account)
  • Nginx to serve the synchronized static files

A few more things that have to be set up

The RabbitMQ team has been looking at the performance differences between the latest RMQ releases. After benchmarking multiple RabbitMQ version/Erlang version/build environment permutations, we have some findings to share.

The new management plugin and stats emission/collection implementation in RabbitMQ 3.6.7 produces a slight drop in performance in some workloads.

Another finding suggests that RabbitMQ packages compiled in Erlang R16B03 (such as the 3.6.x releases produced by our team) will have a minor throughput drop when running on Erlang 20.x. Packages built on Erlang 19.x.x and ran on Erlang 20.x.x showed no such difference.

Dear RabbitMQ community,

We have an update on Erlang/OTP 20 and RabbitMQ compatibility.

First, let's clarify when OTP 20 support will be available: RabbitMQ versions before 3.6.11 will not work correctly with OTP-20.

What's the risk of upgrading from 19.x to 20 on an unsupported version? When upgrading from OTP-19.x(or earlier) to OTP-20 all the persistent data will be permanently lost!

RabbitMQ team is proud to announce that starting from the version 3.7.0 RabbitMQ will come with the new command line tools, known as rabbitmqctl.

The reasoning behind this change is that in previous versions rabbitmqctl was deeply integrated into server code, which made it hard to implement new commands, extend and modify existing commands.

The tools is written on [Elixir][elixir] programming language. This will make it easier for people new to erlang to start extending the tools. Although after built, the tools don't require Elixir to be installed.

Keybase proof

I hereby claim:

  • I am michaelklishin on github.
  • I am michaelklishin (https://keybase.io/michaelklishin) on keybase.
  • I have a public key whose fingerprint is 07CF 80D8 1AE4 711A FF3F 045A E80E DCFA 0CDB 21EE

To claim this, I am signing this object:

+# Add Debian Wheezy backports repository to obtain init-system-helpers
+gpg --keyserver pgpkeys.mit.edu --recv-key 7638D0442B90D010
+gpg -a --export 7638D0442B90D010 | sudo apt-key add -
+echo 'deb http://ftp.debian.org/debian wheezy-backports main' | sudo tee /etc/apt/sources.list.d/wheezy_backports.list
+
+# Add Erlang Solutions repository to obtain esl-erlang
+wget -O- https://packages.erlang-solutions.com/debian/erlang_solutions.asc | sudo apt-key add -
+echo 'deb https://packages.erlang-solutions.com/debian wheezy contrib' | sudo tee /etc/apt/sources.list.d/esl.list
+
+sudo apt-get update
using System;
using System.Threading;
using RabbitMQ.Client;
using RabbitMQ.Client.Framing;
namespace rabbitPublisher
{
class rabbitPublisher
{
public static byte[] TestMessage = new byte[1024];
{ssl_options, [{ciphers, ["ECDHE-ECDSA-AES256-SHA384","ECDHE-RSA-AES256-SHA384",
"ECDH-ECDSA-AES256-SHA384","ECDH-RSA-AES256-SHA384",
"DHE-RSA-AES256-SHA256","DHE-DSS-AES256-SHA256",
"AES256-SHA256","ECDHE-ECDSA-AES128-SHA256",
"ECDHE-RSA-AES128-SHA256","ECDH-ECDSA-AES128-SHA256",
"ECDH-RSA-AES128-SHA256","DHE-RSA-AES128-SHA256",
"DHE-DSS-AES128-SHA256","AES128-SHA256",
"ECDHE-ECDSA-AES256-SHA","ECDHE-RSA-AES256-SHA",
"DHE-RSA-AES256-SHA","DHE-DSS-AES256-SHA",
"ECDH-ECDSA-AES256-SHA","ECDH-RSA-AES256-SHA","AES256-SHA",
[
{rabbit, [
{tcp_listeners, [{"127.0.0.1", 5672}]}
]}
].
[
{ssl, [{versions, ['tlsv1.2', 'tlsv1.1', tlsv1]},
{ciphers, [{dhe_rsa,aes_256_cbc,sha}]}
]},
{rabbit, [
{ssl_listeners, [5672]},
{tcp_listeners, []},
{ssl_options, [{cacertfile,"/path/to/cacert.pem"},
{certfile,"/path/to/server.pem"},