{"action":"created","issue":{"url":"https://api.github.com/repos/celery/django-celery/issues/202","repository_url":"https://api.github.com/repos/celery/django-celery","labels_url":"https://api.github.com/repos/celery/django-celery/issues/202/labels{/name}","comments_url":"https://api.github.com/repos/celery/django-celery/issues/202/comments","events_url":"https://api.github.com/repos/celery/django-celery/issues/202/events","html_url":"https://github.com/celery/django-celery/issues/202","id":7918846,"number":202,"title":"Task cleanup takes forever in MySQL","user":{"login":"kjoconnor","id":731233,"avatar_url":"https://avatars.githubusercontent.com/u/731233?v=3","gravatar_id":"","url":"https://api.github.com/users/kjoconnor","html_url":"https://github.com/kjoconnor","followers_url":"https://api.github.com/users/kjoconnor/followers","following_url":"https://api.github.com/users/kjoconnor/following{/other_user}","gists_url":"https://api.github.com/users/kjoconnor/gists{/gist_id}","starred_url":"https://api.github.com/users/kjoconnor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kjoconnor/subscriptions","organizations_url":"https://api.github.com/users/kjoconnor/orgs","repos_url":"https://api.github.com/users/kjoconnor/repos","events_url":"https://api.github.com/users/kjoconnor/events{/privacy}","received_events_url":"https://api.github.com/users/kjoconnor/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2012-10-28T12:13:00Z","updated_at":"2016-06-03T07:56:16Z","closed_at":null,"body":"We have millions of rows entered into `celery_taskmeta` per day, and then when the cleanup tasks run the queries take a very very long time.  Firstly, is there a reason to update tombstones that are about to be deleted in the next line of code to be hidden?  To hide them from the application while the DELETE is taking place?  This takes a long time, mostly because there's no index on `date_done`.  If the hiding is necessary, maybe there should be an index there?\r\n\r\nI understand the DELETE will just take a long time if you have that many results, but maybe do it in chunks to prevent locking problems?"},"comment":{"url":"https://api.github.com/repos/celery/django-celery/issues/comments/223514940","html_url":"https://github.com/celery/django-celery/issues/202#issuecomment-223514940","issue_url":"https://api.github.com/repos/celery/django-celery/issues/202","id":223514940,"user":{"login":"auvipy","id":6212603,"avatar_url":"https://avatars.githubusercontent.com/u/6212603?v=3","gravatar_id":"","url":"https://api.github.com/users/auvipy","html_url":"https://github.com/auvipy","followers_url":"https://api.github.com/users/auvipy/followers","following_url":"https://api.github.com/users/auvipy/following{/other_user}","gists_url":"https://api.github.com/users/auvipy/gists{/gist_id}","starred_url":"https://api.github.com/users/auvipy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/auvipy/subscriptions","organizations_url":"https://api.github.com/users/auvipy/orgs","repos_url":"https://api.github.com/users/auvipy/repos","events_url":"https://api.github.com/users/auvipy/events{/privacy}","received_events_url":"https://api.github.com/users/auvipy/received_events","type":"User","site_admin":false},"created_at":"2016-06-03T07:56:16Z","updated_at":"2016-06-03T07:56:16Z","body":"@kjoconnor is this problem still exists? if not then we could close this issue."}}
{"actor":{"display_login":"auvipy"}}