99 lines
3.9 KiB
Plaintext
99 lines
3.9 KiB
Plaintext
Release: RabbitMQ 2.0.0
|
|
|
|
Release Highlights
|
|
==================
|
|
|
|
server
|
|
------
|
|
bug fixes
|
|
- correct file descriptor limits on Windows, preventing crashes due to
|
|
exceeding the limit
|
|
- fix bug that resulted in 'rabbitmqctl status' reporting disk nodes
|
|
as ram nodes
|
|
- tx.commit no longer fails when participating queues are deleted
|
|
during the lifetime of the transaction
|
|
- more robust logic to detect changes in the data layout between
|
|
rabbit versions and thus guard against upgrade failures
|
|
|
|
enhancements
|
|
- new persister
|
|
- the volume of messages rabbit can hold on to is bounded by disk
|
|
space (in previous versions it was bounded by memory)
|
|
- rabbit optimises memory usage by paging messages out to / in from
|
|
disk as needed
|
|
- consistently high performance regardless of retained message
|
|
volume (previous versions would slow down considerably as the
|
|
persisted message volume grew)
|
|
- consistently fast startup regardless of volume of persisted data
|
|
(previous versions would require time proportional to the amount
|
|
of data)
|
|
- better performance for concurrent transactions (in previous
|
|
version the rate at which queues could handle transactions
|
|
involving persistent messages was fixed)
|
|
- implement AMQP 0-9-1, in addition to 0-8 - see
|
|
https://www.rabbitmq.com/specification.html
|
|
- instrumentation for asynchronous statistics events, emitting more
|
|
stats than currently available and laying the foundation for
|
|
monitoring a busy broker without crippling performance -
|
|
see https://blog.rabbitmq.com/posts/2010/08/management-monitoring-and-statistics/
|
|
- more effective flow control mechanism that does not require
|
|
cooperation from clients and reacts quickly to prevent the broker
|
|
from exhausing memory - see https://www.rabbitmq.com/extensions.html#memsup
|
|
- implement basic.reject - see
|
|
https://blog.rabbitmq.com/posts/2010/08/well-ill-let-you-go-basicreject-in-rabbitmq/
|
|
- simplify plugin activation by moving it into the server startup
|
|
- permit upgrades of Erlang w/o breaking rabbit servers with activated
|
|
plugins
|
|
- introduce support for queue leases - see https://www.rabbitmq.com/extensions.html#queue-leases
|
|
- improve the setting of permissions, making it easer to use and
|
|
introducing a way to grant no permissions at all - see https://www.rabbitmq.com/admin-guide.html#management
|
|
- delete exclusive queues synchronously on server-initiated connection
|
|
close (rather than just client-initiated)
|
|
|
|
java client
|
|
-----------
|
|
bug fixes
|
|
- prevent spurious timeout exceptions that theoretically could have
|
|
arisen due to spurios thread wake-ups
|
|
|
|
enhancements
|
|
- switch to AMQP 0-9-1 - see
|
|
https://www.rabbitmq.com/specification.html
|
|
|
|
.net client
|
|
-----------
|
|
bug fixes
|
|
- fix bug that caused incorrect responses to server-issued
|
|
channel.flow commands, which in turn resulted in connections getting
|
|
closed with an error.
|
|
- make SSL connections work in Mono
|
|
|
|
enhancements
|
|
- implement AMQP 0-9-1, in addition to 0-8 and 0-9 - see
|
|
https://www.rabbitmq.com/specification.html
|
|
- simplify the Subscription class and make it more versatile
|
|
- improve documentation
|
|
|
|
building & packaging
|
|
--------------------
|
|
bug fixes
|
|
- correct location of rabbitmq.config file under macports - it now
|
|
lives in /opt/local/etc/rabbitmq/
|
|
- "make docs_all" now works on more platforms
|
|
|
|
enhancements
|
|
- portable, binary plugin releases to simplify plugin installation -
|
|
see https://www.rabbitmq.com/plugins.html
|
|
- automatically create plugin directory, to streamline plugin
|
|
installation
|
|
|
|
Upgrading
|
|
=========
|
|
The database schema and the format in which persistent messages are
|
|
stored have both changed since the last release (1.8.1). When
|
|
starting, the RabbitMQ server will detect the existence of an old
|
|
database and will move it to a backup location, before creating a
|
|
fresh, empty database, and will log a warning. If your RabbitMQ
|
|
installation contains important data then we recommend you contact
|
|
rabbitmq-sales@pivotal.io for assistance with the upgrade.
|