Revisions of rabbitmq-server
Fridrich Strba (fstrba)
committed
(revision 206)
Fridrich Strba (fstrba)
accepted
request 1167973
from
Simon Lees (simotek)
(revision 205)
- Update to 3.11.1 * Highlights Khepri now can be used as an alternative schema data store in RabbitMQ, replacing Mnesia MQTTv5 support Support for consumer-side stream filtering A new common message container format used internally, based on the AMQP 1.0 message format Improved classic non-mirrored queue performance with message sizes larger than 4 KiB (or a different customized CQ index embedding threshold) Classic queues storage implementation version 2 (CQv2) is now highly recommended for all new deployments. CQv2 meaningfully improves performance of non-mirrored classic queues for most workloads * Fixes bsc#1222591
buildservice-autocommit
accepted
request 1144783
from
Simon Lees (simotek)
(revision 204)
baserev update by copy to link target
Simon Lees (simotek)
accepted
request 1144564
from
Dominique Leuenberger (dimstar)
(revision 203)
- Provide user/group for RPM 4.19 (boo#1219532).
buildservice-autocommit
accepted
request 1137247
from
Dirk Mueller (dirkmueller)
(revision 202)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
committed
(revision 201)
- update to 3.12.11: * Quorum queue declared when one of cluster nodes was down could trigger connection exceptions. * Avoids a rare exception that could stop TCP socket writes on a client connection. * `queue_deleted` and `queue_created` internal events now include queue type as a module name, and not an inconsistent (with the other queue and stream types) value `classic`. * Definition files that are virtual host-specific cannot be imported on boot. Such files will now be detected early and the import process will terminate after logging a more informative message. * Several AMQP 1.0 application properties are now more correctly converted to AMQP 0-9-1 headers by cross-protocol Shovels. * The priority property now populates an AMQP 1.0 header with the same name, per AMQP 1.0 spec. * Metric label values now escape certain non-ASCII characters. * Avoids an exception when an MQTT client that used a QoS 0 subscription reconnects and its original connection node is down. * Avoids an exception when an MQTT client connection was force- closed via the HTTP API. * Certain CLI commands could not be run in a shell script loop, unless the script explicitly redirected standard input. * `rabbitmq-diagnostics cluster_status` now responds much quicker when a cluster node has gone down, were shut down, or otherwise has become unreachable by the rest of the cluster. * Reverted a change to `DELETE /api/queues/{vhost}/{name}` that allowed removal of exclusive queues and introduced
buildservice-autocommit
accepted
request 1133729
from
Dirk Mueller (dirkmueller)
(revision 200)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
committed
(revision 199)
- update to 3.12.10: * Avoids two Shovels being started after an upgrade from 3.12.6 or older versions. * When a topic permission was deleted, an internal event of type permission.deleted was emitted in some cases, instead of topic.permission.deleted. * Shovels on 3.12.8 nodes failed during a rolling cluster upgrade due to internal identifier format changes. * Avoids an unnecessary warning in the logs. * avoids a potential exception in the autoheal partition handler. * raft.segment_max_entries is now validated to prevent the value from overflowing its 16-bit segment file field. Maximum supported value is now 65535.
buildservice-autocommit
accepted
request 1121010
from
Dirk Mueller (dirkmueller)
(revision 198)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
committed
(revision 197)
- update to 3.12.7: * Stream replication connections configured to use exclusively TLSv1.3 failed. * On startup, stream replicas will handle one more potential case of segment file corruption after an unclean shutdown. * `default_policies.*.queue_pattern` definition in `rabbitmq.conf` was incorrectly parsed. * Avoid log noise when inter-node connections frequently fail and recover. * Optimized stream index scans. Longer scans could result in some replicas stopping with a timeout. * Classic queue storage version is now a supported key for operator policies. * Queue length limit overflow behavior now can be configured via operator policies. * Several `list_stream_*` commands (available via both `rabbitmq-diagnostics` and `rabbitmq-streams`) commands now can display replica node in addition to other fields. * `rabbitmqctl add_user` now can accept a pre-generated salted password instead of a plain text password, both as a positional argument and via standard input: * Message consumption with the "Nack message, requeue: true" option did not actually requeue deliveries. * HTTP API request body size is now limited to 10 MiB by default. * Two endpoints, one that accepts messages for publishing (note: publishing over the HTTP API is greatly discouraged) * and another for definition import, * will now reject larger transfers with a `400 Bad Request` response.
buildservice-autocommit
accepted
request 1099488
from
Dirk Mueller (dirkmueller)
(revision 196)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
accepted
request 1099317
from
Matwey Kornilov (matwey)
(revision 195)
- Improve erlang-rabbitmq-client Provides: The package provides two erlang applications: amqp_client and rabbit_common which are expected to be Required as erlang-%{appname}
buildservice-autocommit
accepted
request 1090956
from
Fusion Future (fusionfuture)
(revision 194)
baserev update by copy to link target
Fusion Future (fusionfuture)
accepted
request 1090948
from
Fusion Future (fusionfuture)
(revision 193)
- Update to 3.12.0 * Optimizations for both quorum and classic queues: improved throughput, lower throughput variability, lower latency, lower memory footprint * More mature and efficient implementation of (non-mirrored) classic queues v2 (CQv2) * Classic queue lazy and non-lazy modes no longer apply: classic queues v2 always behave very similarly * to the lazy mode in earlier release series: moving data to disk aggressively and only keeping a subset of data in memory * Significantly reduced MQTT and Web MQTT memory footprint per connection * OAuth 2, OIDC, IDP support * Even more configurability of the OAuth 2 plugin - More bugfixes and enhancements: https://www.rabbitmq.com/changelog.html
buildservice-autocommit
accepted
request 1035475
from
Fusion Future (fusionfuture)
(revision 192)
baserev update by copy to link target
Fusion Future (fusionfuture)
accepted
request 1035474
from
Fusion Future (fusionfuture)
(revision 191)
- Update to 3.11.3 + Core Server * Stream unsubscription leaked metric counters. * Stream could become unavailable in certain node or network failure scenarios. * It is now possible to pre-configure virtual host limits for groups of virtual hosts. * Quorum queue replicas no longer try to contact their unreachable peers for metrics. + CLI Tools * rabbitmq-diagnostics status now handles server responses where free disk space is not yet computed. * All enabled (explicitly or as a dependency) plugins are scanned. * rabbitmq-diagnostics memory_breakdown now returns results much faster in environments with a large number of quorum queues.
buildservice-autocommit
accepted
request 1031374
from
Fridrich Strba (fstrba)
(revision 190)
baserev update by copy to link target
Fridrich Strba (fstrba)
accepted
request 1031341
from
Dominique Leuenberger (dimstar)
(revision 189)
- Update to version 3.10.10: + Core Server * Partially reverts an unsafe inter-node communication optimization that could affect classic mirrored queue operation ordering. * Classic mirrored queue leader replica issued to much credit to follower replicas, resulting in an uneven load and memory footprint between them. * Intra-cluster communication link metric collector could run into an exception when peer connection has just been re-established, e.g. after a peer node restart. + MQTT Plugin * When a node was put into maintenance mode, it closed all MQTT client connections cluster-wide instead of just local client connections. - For updates between 3.10.5 and 3.10.9, please see https://www.rabbitmq.com/changelog.html
buildservice-autocommit
accepted
request 983568
from
Dirk Mueller (dirkmueller)
(revision 188)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
accepted
request 983566
from
Fusion Future (fusionfuture)
(revision 187)
- Update to 3.10.5 * Quorum queue could run into an exception when dead lettering a message under certain conditions. - Changes from 3.10.4 * Avoid seeding default user in old clusters that still use the deprecated management.load_definitions option. * Streams could run into an exception or fetch stale stream position data in some scenarios. * rabbitmqctl set_log_level did not have any effect on logging via amq.rabbitmq.log
Displaying revisions 1 - 20 of 206