7

I am developing an RabbitMQ consumer with pika 0.10.0, and python 2.7 version.In my consumer client, I have a process that runs for a time period depending on input message. It can vary from 3 to 40 minutes. I do not want to disable heartbeat. Instead I am looking for some collback mechanism that can keep the connection alive until the delivery_tag is sent back. Is that possible?

Few link I got, all are suggesting to disable the heartbeat as workaround. But I do not want to disable it.

Ref:

Socket Error: 104 consuming messages with task that take a long time #753

BlockingConnection gets closed unexpectedly #734

Also, please let me know if any extra information is required. Thanks in advance.

Anirban B
  • 507
  • 8
  • 27
  • Possible duplicate of [Handling long running tasks in pika / RabbitMQ](https://stackoverflow.com/questions/14572020/handling-long-running-tasks-in-pika-rabbitmq) – Demircan Celebi Feb 21 '19 at 12:52

1 Answers1

11

The only solution is to send heartbeat frames periodically.

When using a BlockingConnection, you have to call the process_data_events function frequently enough (a time_limit of zero is ok). When using a SelectConnection or other async adapters, you have to ensure none of your processes are blocking, so that frames can be sent.

If your task is long running and you can't interrupt or split the process easily for some reason, you can run the task in another thread/process, and still have pika sending frames from the main thread. Just keep in mind that you should avoid using pika connections across threads (pika is not thread-safe at the moment).

user8808265
  • 1,893
  • 1
  • 17
  • 25