未加星标

Dealing with database transactions in Django + Celery

字体大小 | |
[开发(python) 所属分类 开发(python) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

Celery is an asynchronous task queue/job queue based on distributed message passing. We are big fans of Celery and it’s an important part of our stack. As with any distributed system, Celery comes with it’s own set of challenges. In this post, I specifically want to discuss how we use Celery to push webhooks to our customers and the race conditions caused because of using database transactions.

The Webhook Architecture

We generate alerts for delays on the way and push these events over webhooks. Depending on the event, different entities in the database get updated and an event object is stored in the db. We then put the event id on RabbitMQ where it is picked up by one of our worker nodes and pushed to the webhook URL.


Dealing with database transactions in Django + Celery

The Transaction Race Condition

As you can imagine, all of these updates have to be done in a transaction to guarantee the database is in the correct state. This is what our code looked like:

Once deployed, we started noticing the following error, intermittently:

Error: Task events.jobs.push_event (837a1d29-4821-2b9e-844f-b8e5b40657): “DoesNotExist(‘Event matching query does not exist.’, )

The task was being picked up by the worker before the transaction was complete. Because our isolation level was set at READ COMMITTED , the event from the uncommitted transaction was not visible to the worker and hence the task was failing. We needed to put the event on the queue AFTER the transaction had been committed.

The Solution

Starting version 1.9, Django has introduced the on_commit hook for transactions. We canpass a function to this hook and it willbe called when the transaction is successfully committed. To be able to use this across different tasks, we use an abstract Celery task class that we call the TransactionAwareTask . Using this, we can ensure that our tasks arefired only after the transaction has been committed. Thisis what our code looks like now:

This solution is simple and generic enough that it can be used across a variety of tasks and it hasn’t let us down since.

Have questions? Suggestions? Join the discussion onslack.

Like what we are doing? Sign up to use HyperTrack and build location tracking features!

本文开发(python)相关术语:python基础教程 python多线程 web开发工程师 软件开发工程师 软件开发流程

主题: DjangoRabbitMQ
分页:12
转载请注明
本文标题:Dealing with database transactions in Django + Celery
本站链接:http://www.codesec.net/view/480152.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 开发(python) | 评论(0) | 阅读(42)