RabbitMQ 3.7.8 RC3 发布了，这是一个维护版本，侧重于 bug 修复和进一步提高 Erlang/OTP 21 的兼容性，由于 RabbitMQ 3.7.7 之前版本的 CLI 工具无法在 Erlang 21 中工作，因此必须在升级 Erlang 之前先升级 RabbitMQ。
Virtual host (specifically binding) recovery has been optimized.
A queue sync operation now can becancelledwhen a resource alarm is in effect on the receiving node.
Inter-node communication port (a.k.a. distribution port) unintentionally used an excessively large
buffer size (1.2 GB instead of 128 MB). Kudos to Chris Friesen for noticing and reporting this.
A resource alarm triggered during boot could preventnodefrom starting.
Syslog configuration parameters could be rejected by config validator.
On Erlang/OTP 21 Syslog server now can be configured using a hostname (not just an IP address).
rabbitmqctl rename_cluster_node documentation improvements.
Policies were unintentionally excludedfrom
rabbitmqctl report output.
Virtual host imported from definitions or created via HTTP API will explicitlyawaitfor thevhosttoinitialise
on all cluster nodes. This change was previously scheduled for
3.7.6 but was only partially applied (didn't have
any effect on HTTP API clients).
HTTP API connection endpoints returned a duplicate key,
Cowboy timeouts now can be configured.
rabbitmqadmin now supports a new argument,
Switching sections will now scroll to the top of the newly rendered page.
Nodes experiencing very high connection churn could run out of Erlang processes.
Improved OTPreleasehandling compatibility.
Link initialization optimizations.
It is now possible to set up a tracer on any cluster node via management UI and HTTP API.
Tracer connection credentials now can be specified via the management UI and HTTP API.