发布于 2015-09-25 07:31:48 | 76 次阅读 | 评论: 0 | 来源: 网友投递

这里有新鲜出炉的RabbitMQ 能为你做些什么?,程序狗速度看过来!

RabbitMQ 开源消息队列系统

RabbitMQ 是由 LShift 提供的一个 Advanced Message Queuing Protocol (AMQP) 的开源实现,由以高性能、健壮以及可伸缩性出名的 Erlang 写成,因此也是继承了这些优点。


RabbitMQ 3.5.5 正式发布,此版本除了常规的 bug 修复之外,提升了队列页面信息到磁盘的速度。

UPDATE 2:新 RPM 和 Debian 包已经附在发行说明里面,主要修复了两个回退问题:

UPDATE 1:移除了 RPM 和 Debian 包,因为一个 shell 脚本包括一个 Bash 行。

服务器

功能增强

  • Improve performance when a queue's journal is written to disk (rabbitmq/rabbitmq-server#227, rabbitmq/rabbitmq-server#289).

  • Improve performance when a queue is purged (rabbitmq/rabbitmq-server#295).

  • Introduce new options to tune the queue paging performance (rabbitmq/rabbitmq-server#284). These are low-level settings and should be handled carefully. Here are the default values:

    
     

    %% In /etc/rabbitmq/rabbitmq.config[  
    {rabbit, [
     {msg_store_credit_disc_bound, {2000, 500}},
     {msg_store_io_batch_size, 2048},
     {credit_flow_default_credit, {200, 50}}
    ]}  
    ].

  • Improve performance when expired messages need to be removed and no dead-letter exchange has been set up, by grouping handling of delivers and ack (rabbitmq/rabbitmq-server#308).

  • Add an option to disable file_handle_cache's read cache (rabbitmq/rabbitmq-server#226). This read cache was reported to be a performance penalty, especially when a starting RabbitMQ slave needs to synchronize and fetch messages from a master node. We now offer an option to disable this cache and we plan to disable it by default in RabbitMQ 3.6.0. Here is how to use this new option:

    
     

    %% In /etc/rabbitmq/rabbitmq.config[  
    {rabbit, [
     {fhc_read_buffering, false}
    ]}  
    ].

  • The queue_index_embed_msgs_below parameter is now read once from the application environment when the queue is created, instead of every time it is needed (rabbitmq/rabbitmq-server#291). This removes a bottleneck by avoiding synchronous calls to the Erlang application server.

  • Reduce default heartbeat interval from 580 to 60 seconds (rabbitmq/rabbitmq-server#297). This is a more sensible default value, after considering what users usually do.

  • Force essential TCP options (rabbitmq/rabbitmq-server#282), especially {reuseaddr, true}. User won't have to copy them when tuning TCP options anymore and this decreases the risk of errors.

  • Catch SIGTERM and other signals in the rabbitmq-server script to stop RabbitMQ gracefully (rabbitmq/rabbitmq-server#234). This mostly targets Docker users. Thanks to Duncan Gordon (@dunk) for reporting the issue!

  • Honor !RABBITMQ_BASE! value for the default location of rabbitmq-env-conf.bat (rabbitmq/rabbitmq-server#239). Thanks to Jared Kauppila (@Jakauppila) for the patch!

  • Warn user if a 32-bit Erlang runtime is used (rabbitmq/rabbitmq-server#251), due to the limited address space and the possible memory shortage.

Bug 修复

插件:Federation

Bug 修复

插件:Management UI

功能增强

Bug 修复

插件:MQTT

功能增强

插件:STOMP

增强

Bug 修复

  • Duplicate subscription IDs no longer result in unhandled exceptions.

客户端库:Java

功能增强

Bug 修复

客户端库:.NET

Bug 修复

升级:http://www.rabbitmq.com/clustering.html#upgrading

下载:

RabbitMQ 是由 LShift 提供的一个 Advanced Message Queuing Protocol (AMQP) 的开源实现,由以高性能、健壮以及可伸缩性出名的 Erlang 写成,因此也是继承了这些优点。

AMQP 里主要要说两个组件:Exchange 和 Queue (在 AMQP 1.0 里还会有变动),如下图所示,绿色的 X 就是 Exchange ,红色的是 Queue ,这两者都在 Server 端,又称作 Broker ,这部分是 RabbitMQ 实现的,而蓝色的则是客户端,通常有 Producer 和 Consumer 两种类型:



历史版本 :
RabbitMQ 3.7.2 发布,修复插件问题
RabbitMQ 3.7.0 发布,正式支持 Erlang/OTP 20
RabbitMQ 3.6.14 发布,常规维护版本
RabbitMQ 3.6.13 发布,常规维护版本
RabbitMQ 3.6.12 发布,AMQP 消息服务器
RabbitMQ 3.6.12 RC2 发布,AMQP 消息服务器
RabbitMQ 3.6.11 发布,AMQP 消息服务器
RabbitMQ 3.6.11 Milestone 5、v3.7.0 milestone18 发布
RabbitMQ 3.6.11 Milestone 3 发布
RabbitMQ v3.6.11 milestone2 发布,AMQP 消息服务器
RabbitMQ 3.6.10 正式发布,AMQP 消息服务器
RabbitMQ 3.6.10 Milestone 4 发布
最新网友评论  共有(0)条评论 发布评论 返回顶部

Copyright © 2007-2017 PHPERZ.COM All Rights Reserved   冀ICP备14009818号  版权声明  广告服务