I've recently seen a somewhat similar situation: - Celery went down for a while.
- Celerybeat jobs accumulated in RabbitMQ. - When Celery came back up, it spun manically, going through hundreds of old jobs. However, neither Celery nor RabbitMQ showed signs of falling over. They were just busy. It's a separate bug, but we should ensure that Celerybeat jobs have a very short lifetime. Maybe RabbitMQ or Celery have a mechanism for ignoring old jobs. If not, we can add a timestamp check to the job implementations themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153077 Title: rabbitmq queue fills up and celery stops executing tasks when upload_dhcp_leases is done every minute (by default) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1153077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
