RabbitMQ tutorial - Work Queues

Work Queues

(using the Objective-C client)

info

Prerequisites

This tutorial assumes RabbitMQ is installed and running on localhost on the standard port (5672). In case you use a different host, port or credentials, connections settings would require adjusting.

Where to get help

If you're having trouble going through this tutorial you can contact us through the mailing list or RabbitMQ community Slack.

In the first tutorial we wrote methods to send and receive messages from a named queue. In this one we'll create a Work Queue that will be used to distribute time-consuming tasks among multiple workers.

The main idea behind Work Queues (aka: Task Queues) is to avoid doing a resource-intensive task immediately and having to wait for it to complete. Instead we schedule the task to be done later. We encapsulate a task as a message and send it to a queue. A worker process running in the background will pop the tasks and eventually execute the job. When you run many workers the tasks will be shared between them.

This concept is especially useful in web applications where it's impossible to handle a complex task during a short HTTP request window.

Preparation

In the previous part of this tutorial we sent a message containing "Hello World!". Now we'll be sending strings that stand for complex tasks. We don't have a real-world task, like images to be resized or pdf files to be rendered, so let's fake it by just pretending we're busy - by using sleep. We'll take the number of dots in the string as its complexity; every dot will account for one second of "work". For example, a fake task described by Hello... will take three seconds.

We will slightly modify the send method from our previous example, to allow an arbitrary string to be sent as a method parameter. This method will schedule tasks to our work queue, so let's rename it to newTask. The implementation remains the same apart from the new parameter:

func newTask(_ msg: String) {
    let conn = RMQConnection(delegate: RMQConnectionDelegateLogger())
    conn.start()
    let ch = conn.createChannel()
    let q = ch.queue("task_queue", options: .durable)
    let msgData = msg.data(using: .utf8)
    ch.defaultExchange().publish(msgData, routingKey: q.name, persistent: true)
    print("Sent \(msg)")
    conn.close()
}

Our old receive method requires some bigger changes: it needs to fake a second of work for every dot in the message body. It will help us understand what's going on if each worker has a name, and each will need to pop messages from the queue and perform the task, so let's call it workerNamed():

q.subscribe({(_ message: RMQMessage) -> Void in
    let messageText = String(data: message.body, encoding: .utf8)
    print("\(name): Received \(messageText)")
    // imitate some work
    let sleepTime = UInt(messageText.components(separatedBy: ".").count) - 1
    print("\(name): Sleeping for \(sleepTime) seconds")
    sleep(sleepTime)
})

Note that our fake task simulates execution time.

Run them from viewDidLoad as in tutorial one:

override func viewDidLoad() {
    super.viewDidLoad()
    self.newTask("Hello World...")
    self.workerNamed("Flopsy")
}

The log output should indicate that Flopsy is sleeping for three seconds.

Round-robin dispatching

One of the advantages of using a Task Queue is the ability to easily parallelise work. If we are building up a backlog of work, we can just add more workers and that way, scale easily.

Let's try to run two workerNamed() methods at the same time. They will both get messages from the queue, but how exactly? Let's see.

Change viewDidLoad to send more messages and start two workers:

override func viewDidLoad() {
    super.viewDidLoad()
    self.workerNamed("Jack")
    self.workerNamed("Jill")
    self.newTask("Hello World...")
    self.newTask("Just one this time.")
    self.newTask("Five.....")
    self.newTask("None")
    self.newTask("Two..dots")
}

Let's see what is delivered to our workers:

# => Jack: Waiting for messages
# => Jill: Waiting for messages
# => Sent Hello World...
# => Jack: Received Hello World...
# => Jack: Sleeping for 3 seconds
# => Sent Just one this time.
# => Jill: Received Just one this time.
# => Jill: Sleeping for 1 seconds
# => Sent Five.....
# => Sent None
# => Sent Two..dots
# => Jill: Received Five.....
# => Jill: Sleeping for 5 seconds
# => Jack: Received None
# => Jack: Sleeping for 0 seconds
# => Jack: Received Two..dots
# => Jack: Sleeping for 2 seconds

By default, RabbitMQ will send each message to the next consumer, in sequence. On average every consumer will get the same number of messages. This way of distributing messages is called round-robin. Try this out with three or more workers.

Message acknowledgment

Doing a task can take a few seconds, you may wonder what happens if a consumer starts a long task and it terminates before it completes. With our current code, once RabbitMQ delivers a message to the consumer, it immediately marks it for deletion. In this case, if you terminate a worker, the message it was just processing is lost. The messages that were dispatched to this particular worker but were not yet handled are also lost.

But we don't want to lose any tasks. If a worker dies, we'd like the task to be delivered to another worker.

In order to make sure a message is never lost, RabbitMQ supports message acknowledgments. An ack(nowledgement) is sent back by the consumer to tell RabbitMQ that a particular message has been received, processed and that RabbitMQ is free to delete it.

If a consumer dies (its channel is closed, connection is closed, or TCP connection is lost) without sending an ack, RabbitMQ will understand that a message wasn't processed fully and will re-queue it. If there are other consumers online at the same time, it will then quickly redeliver it to another consumer. That way you can be sure that no message is lost, even if the workers occasionally die.

A timeout (30 minutes by default) is enforced on consumer delivery acknowledgement. This helps detect buggy (stuck) consumers that never acknowledge deliveries. You can increase this timeout as described in Delivery Acknowledgement Timeout.

Message acknowledgments are turned off by default in the client, but not in the AMQ protocol (the RMQBasicConsumeOptions.noAck option is automatically sent by subscribe()). It's time to turn acknowledgements on by explicitly setting an empty RMQBasicConsumeOptions and sending a proper acknowledgment from the worker once we're done with a task.

let manualAck = RMQBasicConsumeOptions()
q.subscribe(manualAck, handler: {(_ message: RMQMessage) -> Void in
    let messageText = String(data: message.body, encoding: .utf8)
    print("\(name): Received \(messageText)")
    // imitate some work
    let sleepTime = UInt(messageText.components(separatedBy: ".").count) - 1
    print("\(name): Sleeping for \(sleepTime) seconds")
    sleep(sleepTime)
    ch.ack(message.deliveryTag)
})

Using this code we can be sure that even if a worker dies while it was processing a message, nothing will be lost. Soon after the worker dies all unacknowledged messages will be redelivered.

Acknowledgement must be sent on the same channel that received the delivery. Attempts to acknowledge using a different channel will result in a channel-level protocol exception. See the doc guide on confirmations to learn more.

Forgotten acknowledgment

It's a common mistake to miss the ack. It's an easy error, but the consequences are serious. Messages will be redelivered when your client quits (which may look like random redelivery), but RabbitMQ will eat more and more memory as it won't be able to release any unacked messages.

In order to debug this kind of mistake you can use rabbitmqctl to print the messages_unacknowledged field:

sudo rabbitmqctl list_queues name messages_ready messages_unacknowledged

On Windows, drop the sudo:

rabbitmqctl.bat list_queues name messages_ready messages_unacknowledged

Message durability

We have learned how to make sure that even if the consumer dies, the task isn't lost. But our tasks will still be lost if RabbitMQ server stops.

When RabbitMQ quits or crashes it will forget the queues and messages unless you tell it not to. Two things are required to make sure that messages aren't lost: we need to mark both the queue and messages as durable.

First, we need to make sure that the queue will survive a RabbitMQ node restart. In order to do so, we need to declare it as durable:

let q = ch.queue("hello", options: .durable)

Although this command is correct by itself, it won't work in our present setup. That's because we've already defined a queue called hello which is not durable. RabbitMQ doesn't allow you to redefine an existing queue with different parameters and will return an error to any program that tries to do that. But there is a quick workaround - let's declare a queue with different name, for example task_queue:

var q = ch.queue("task_queue", options: .durable)

This options: .durable change needs to be applied to both the producer and consumer code.

At this point we're sure that the task_queue queue won't be lost even if RabbitMQ restarts. Now we need to mark our messages as persistent

• by using the persistent option.

ch.defaultExchange().publish(msgData, routingKey: q.name, persistent: true)

Note on message persistence

Marking messages as persistent doesn't fully guarantee that a message won't be lost. Although it tells RabbitMQ to save the message to disk, there is still a short time window when RabbitMQ has accepted a message and hasn't saved it yet. Also, RabbitMQ doesn't do fsync(2) for every message -- it may be just saved to cache and not really written to the disk. The persistence guarantees aren't strong, but it's more than enough for our simple task queue. If you need a stronger guarantee then you can use publisher confirms.

Fair dispatch

You might have noticed that the dispatching still doesn't work exactly as we want. For example in a situation with two workers, when all odd messages are heavy and even messages are light, one worker will be constantly busy and the other one will do hardly any work. Well, RabbitMQ doesn't know anything about that and will still dispatch messages evenly.

This happens because RabbitMQ just dispatches a message when the message enters the queue. It doesn't look at the number of unacknowledged messages for a consumer. It just blindly dispatches every n-th message to the n-th consumer.

In order to defeat that we can use the basicQos(global:) method with the prefetch value of @1. This tells RabbitMQ not to give more than one message to a worker at a time. Or, in other words, don't dispatch a new message to a worker until it has processed and acknowledged the previous one. Instead, it will dispatch it to the next worker that is not still busy.

ch.basicQos(1, global: false)

Note about queue size

If all the workers are busy, your queue can fill up. You will want to keep an eye on that, and maybe add more workers, or have some other strategy.

Putting it all together

Final code of our newTask() method:

func newTask(_ msg: String) {
    let conn = RMQConnection(delegate: RMQConnectionDelegateLogger())
    conn.start()
    let ch = conn.createChannel()
    let q = ch.queue("task_queue", options: .durable)
    let msgData = msg.data(using: .utf8)
    ch.defaultExchange().publish(msgData, routingKey: q.name, persistent: true)
    print("Sent \(msg)")
    conn.close()
}

And our workerNamed():

func workerNamed(_ name: String) {
    let conn = RMQConnection(delegate: RMQConnectionDelegateLogger())
    conn.start()
    let ch = conn.createChannel()
    let q = ch.queue("task_queue", options: .durable)
    ch.basicQos(1, global: false)
    print("\(name): Waiting for messages")
    let manualAck = RMQBasicConsumeOptions()
    q.subscribe(manualAck, handler: {(_ message: RMQMessage) -> Void in
        let messageText = String(data: message.body, encoding: .utf8)
        print("\(name): Received \(messageText)")
        // imitate some work
        let sleepTime = UInt(messageText.components(separatedBy: ".").count) - 1
        print("\(name): Sleeping for \(sleepTime) seconds")
        sleep(sleepTime)
        ch.ack(message.deliveryTag)
    })
}

(source)

Using message acknowledgments and prefetch you can set up a work queue. The durability options let the tasks survive even if RabbitMQ is restarted.

Now we can move on to tutorial 3 and learn how to deliver the same message to many consumers.