Menu

RabbitMQ Erlang Version Requirements

Introduction

This guide covers Erlang/OTP version requirements, Erlang version support policy, a RabbitMQ/Erlang compatibility matrix, version-specific notes and ways of provisioning recent Erlang/OTP releases.

Supported Erlang Version Policy

Starting in January 2019, RabbitMQ supports two most recent Erlang release series: 22.x and 21.3.x.

RabbitMQ and Erlang/OTP Compatibility Matrix

The table below provides an Erlang compatibility matrix of currently supported RabbitMQ release series. For RabbitMQ releases that have reached end of life, see Unsupported Series Compatibility Matrix.

RabbitMQ version Minimum required Erlang/OTP Maximum supported Erlang/OTP Notes
  • 3.8.1
  • 3.8.0
  • 21.3.x
  • 22.x
  • Erlang 22.1 is recommended.
  • Erlang 22.x dropped support for HiPE
  • 3.7.21
  • 3.7.20
  • 3.7.19
  • 21.3.x
  • 22.x
  • 3.7.18
  • 3.7.17
  • 3.7.16
  • 3.7.15
  • 20.3.x
  • 22.x
  • 3.7.14
  • 3.7.13
  • 3.7.12
  • 3.7.11
  • 3.7.10
  • 3.7.9
  • 3.7.8
  • 3.7.7
  • 20.3.x
  • 21.3.x
  • 3.7.6
  • 3.7.5
  • 3.7.4
  • 3.7.3
  • 3.7.2
  • 3.7.1
  • 3.7.0
  • 19.3.x
  • 20.3.x
  • For the best TLS support, the latest version of Erlang/OTP 20.3.x is recommended
  • Erlang versions prior to 19.3.6.4 have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
  • Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
  • On Windows, Erlang/OTP 20.2 changed default cookie file location

As a rule of thumb, most recent patch versions of each supported Erlang/OTP series is recommended.

Provisioning Latest Erlang Releases

Most recent versions can be obtained from a number of sources:

Installing Erlang/OTP on Debian or Ubuntu

Standard Debian and Ubuntu repositories provide Erlang/OTP but it is heavily sliced and diced into dozens of packages. In addition, unless the system has backport repositories enabled, the versions tend to be quite old. See Debian and Ubuntu installation guide for more information on the essential packages, dependencies, and alternative apt repositories.

Installing Erlang/OTP on RHEL, CentOS and Fedora

There are multiple RPM packages available for Erlang/OTP. The recommended option is the zero-dependency Erlang RPM from the RabbitMQ team. It closely follows the latest Erlang/OTP patch release schedule.

See CentOS, RHEL and Fedora installation guide for more information on the available options.

Erlang Versions in Clusters

It is highly recommended that the same major version of Erlang is used across all cluster nodes (e.g. 22.x).

RabbitMQ will check for internal protocol versions of Erlang and its distributed libraries when a node joins a cluster, refusing to cluster if there's a potentially incompatible combination detected.

Outside of a reasonably long upgrade time wiindow, it is recommended that all nodes use exactly the same version of Erlang.

HiPE (JIT Compilation)

HiPE support has been dropped in Erlang 22. RabbitMQ no longer supports HiPE precompilation.

Building Erlang from Source

If a sufficiently recent Erlang package is not available for a given operating system, Erlang/OTP can be built from source. This requires a build environment that satisfies the Erlang build dependencies, such as a modern OpenSSL version.

kerl makes building Erlang/OTP releases from source, including specific tags from GitHub, a much more pleasant experience.

Older RabbitMQ and Erlang Releases

Unsupported RabbitMQ Series

Unsupported RabbitMQ Series Minimum required Erlang/OTP Maximum supported Erlang/OTP Notes
  • 3.6.16
  • 3.6.15
  • 19.3
  • 20.3.x
  • RabbitMQ 3.6 was released on 2015-12-22, and reached end of life on 2018-05-31, we strongly discourage its use
  • On Windows, Erlang/OTP 20.2 changed default cookie file location
  • Versions prior to 19.3.6.4 have known bugs (e.g. ERL-430, ERL-448) that can prevent RabbitMQ nodes from accepting connections (including from CLI tools) and stopping
  • Versions prior to 19.3.6.4 are vulnerable to the ROBOT attack (CVE-2017-1000385)
  • 3.6.14
  • 3.6.13
  • 3.6.12
  • 3.6.11
  • R16B03
  • 20.1.x
  • RabbitMQ 3.6 was released on 2015-12-22, and reached end of life on 2018-05-31, we strongly discourage its use
  • 3.6.10
  • 3.6.9
  • 3.6.8
  • 3.6.7
  • 3.6.6
  • 3.6.5
  • 3.6.4
  • R16B03
  • 19.3.x
  • RabbitMQ 3.6 was released on 2015-12-22, and reached end of life on 2018-05-31, we strongly discourage its use
  • 3.6.3
  • 3.6.2
  • 3.6.1
  • 3.6.0
  • R16B03
  • 18.3.x
  • RabbitMQ 3.6 was released on 2015-12-22, and reached end of life on 2018-05-31, we strongly discourage its use
  • 3.5.x
  • R14B04
  • 17.5.x
  • RabbitMQ 3.5 was released on 2015-03-11, and reached end of life on 2016-10-31, we strongly discourage its use
  • 3.4.x
  • R13B03
  • 16B03
  • RabbitMQ 3.4 was released 2014-10-21, and reached end of life 2015-10-31, we strongly discourage its use

Last Version to Support R16B03

If you absolutely must use an older version of Erlang, RabbitMQ 3.6.14 is the newest version compatible with R16B03.

Last Version to Support R13B03

If you absolutely must use an older version of Erlang, RabbitMQ 3.5.8 is the newest version compatible with R13B03.

Getting Help and Providing Feedback

If you have questions about the contents of this guide or any other topic related to RabbitMQ, don't hesitate to ask them on the RabbitMQ mailing list.

Help Us Improve the Docs <3

If you'd like to contribute an improvement to the site, its source is available on GitHub. Simply fork the repository and submit a pull request. Thank you!