Zum Inhalt springen

RabbitMQ Release Notes

5 Einträge aus 1 Quelle. Zuletzt aktualisiert:

Feed abonnieren:RSS: Feed für RabbitMQ Release NotesAPI: Einträge von RabbitMQ Release Notes als JSON
Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

RabbitMQ

RabbitMQ 4.3.6: Exchange-Bindings und Quorum-Queue-Replikate korrigiert

RabbitMQ 4.3.6 ist ein Wartungsrelease, das behebt, dass beim Löschen eines Exchange die Bindings, die ihn als Ziel hatten, nicht mitgelöscht wurden, und das zudem das Quorum-Queue-Membership-Reconciliation korrigiert, die mehr Replikate als das konfigurierte Ziel hinzufügen konnte.

RabbitMQ 4.3.6 is a maintenance release in the 4.3.x release series.

It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0.

Minimum Supported Erlang Version

The minimum supported Erlang version for this release series is 27.0.

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • Deleting an exchange did not delete the bindings that pointed to it as a destination. A few related cases around auto-delete exchanges, transient queue cleanup and virtual host deletion were fixed along the way.

    GitHub issues: #17255, #17257

  • Quorum queue continuous membership reconciliation could add more replicas than the configured target. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

RabbitMQ

RabbitMQ 4.3.5: Doppelte Zustellungen bei direct reply-to behoben

RabbitMQ 4.3.5 ist ein Wartungsrelease, das unter anderem doppelte Zustellungen bei direct reply-to sowie eine teilweise initialisierte interne Quorum-Queue-Struktur nach der Wiederherstellung aus einem Checkpoint behebt.

RabbitMQ 4.3.5 is a maintenance release in the 4.3.x release series.

It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0.

Minimum Supported Erlang Version

The minimum supported Erlang version for this release series is 27.0.

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • With direct reply-to, a message routed to multiple targets that resolved to the same process could be delivered to it more than once.

    GitHub issue: #17071

  • Quorum queue recovery from a recovery checkpoint could leave a part of the queue's internal state only partially initialized.

    GitHub issue: #17012

  • In clusters that run a mix of 4.2.x and 4.3.x nodes during a rolling upgrade, …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

RabbitMQ

RabbitMQ 4.3.4: Quorum-Queue-Metriken nach Upgrade und AMQP-1.0-Parser

RabbitMQ 4.3.4 ist ein Wartungsrelease, das behebt, dass Quorum Queues nach einem Knotenneustart in von 3.13.x über 4.2.x auf 4.3.x aktualisierten Clustern keine Metriken und Snapshots mehr erzeugten, und das den AMQP-1.0-Parser strenger und effizienter macht.

RabbitMQ 4.3.4 is a maintenance release in the 4.3.x release series.

It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0.

Minimum Supported Erlang Version

The minimum supported Erlang version for this release series is 27.0.

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • Quorum queues in clusters upgraded from 3.13.x to 4.2.x and then to 4.3.x could stop emitting metrics and taking snapshots after a node restart.

    GitHub issues: #16974, #16990

  • The AMQP 1.0 parser now detects standard message body sections more strictly.

    GitHub issue: #17017

  • The AMQP 1.0 parser now decodes certain array values more efficiently. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

RabbitMQ

RabbitMQ 4.2.9: Erlang 27.0 als Mindestversion und Pfadfix

RabbitMQ 4.2.9 ist ein Wartungsrelease, das ab sofort Erlang 27.0 als Mindestversion voraussetzt, die Anhäufung von Schrägstrichen in Classic-Queue-Index-Pfaden (enametoolong-Fehler) behebt und bei AMQP-1.0-Management-Operationen die Berechtigungen für Alternate Exchanges wie bei AMQP 0-9-1 prüft.

RabbitMQ 4.2.9 is a maintenance release in the 4.2.x release series.

It is strongly recommended that you read 4.2.0 release notes in detail if upgrading from a version prior to 4.2.0.

Minimum Supported Erlang Version

Important: starting with this release, the minimum supported Erlang version is 27.0. Erlang/OTP 26 has reached end of life and is no longer supported.

GitHub issue: #16914

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • Classic queue index directory paths could accumulate slashes, eventually failing with an enametoolong file system error.

    GitHub issue: #16833

  • AMQP 1.0 management operations that declare an exchange with an alternate exchange now verify the necessary permissions on the alternate exchange, matching AMQP 0-9-1. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

RabbitMQ

RabbitMQ 4.3.3: Erlang 27.0 Pflicht, Raft-Commit- und Dead-Letter-Fixes

RabbitMQ 4.3.3 ist ein Wartungsrelease, das ab sofort Erlang 27.0 als Mindestversion voraussetzt und behebt, dass Raft-Leader neue Log-Einträge in bestimmten Szenarien vorzeitig committen konnten sowie dass At-least-once-Dead-Lettering bei Quorum Queues nach wiederholten Membership-Änderungen dauerhaft hängen konnte.

RabbitMQ 4.3.3 is a maintenance release in the 4.3.x release series.

It is strongly recommended that you read 4.3.0 release notes in detail if upgrading from a version prior to 4.3.0.

Minimum Supported Erlang Version

Important: starting with this release, the minimum supported Erlang version is 27.0. Erlang/OTP 26 has reached end of life and is no longer supported.

GitHub issue: #16914

RabbitMQ and Erlang/OTP Compatibility Matrix has more details on Erlang version requirements for RabbitMQ.

Nodes will fail to start on older Erlang releases.

Changes Worth Mentioning

Release notes can be found on GitHub at rabbitmq-server/release-notes.

Core Server

Bug Fixes

  • Quorum queue, Khepri and other Raft leaders could optimistically commit new log entries in certain scenarios.

    GitHub issue: rabbitmq/ra#637

  • Quorum queues that use at-least-once dead lettering could get their dead lettering process permanently stuck after repeated queue membership changes. …

Originalquelle(öffnet in neuem Tab)Problem melden

Ähnlich wie RabbitMQ, mit neuen Einträgen