![]() If rebooted, overutilized brokers might become unresponsive in the REBOOT_IN_PROGRESS state. When a broker is overutilized, rebooting an Amazon MQ for RabbitMQ broker can cause further degradation of performance. In cluster deployments, queues with a large number of messages can lead to resource overutilization. The following example demonstrates declaring a lazy queue using the RabbitMQ Java client library. You can enable lazy queues by setting the clare arguments at the time of declaration, or by configuring a policy via the RabbitMQ management console. To disk as lazy queues store messages to disk as soon as possible, resulting in fewer messages cached in memory. Enabling lazy queues can have a significant impact on speeding up the process of moving messages Memory to disk can take time and stops the queue from processing messages. RabbitMQ's default behavior is to cache messages in memory and to move them to disk only when the broker needs more available memory. If you are working with very long queues that process large volumes of messages, enabling lazy queues can improve your broker's overall performance.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |