{"action":"created","issue":{"url":"https://api.github.com/repos/celery/celery/issues/2840","repository_url":"https://api.github.com/repos/celery/celery","labels_url":"https://api.github.com/repos/celery/celery/issues/2840/labels{/name}","comments_url":"https://api.github.com/repos/celery/celery/issues/2840/comments","events_url":"https://api.github.com/repos/celery/celery/issues/2840/events","html_url":"https://github.com/celery/celery/pull/2840","id":109938155,"number":2840,"title":"Fix issue #1628","user":{"login":"mpermana","id":1491836,"avatar_url":"https://avatars.githubusercontent.com/u/1491836?v=3","gravatar_id":"","url":"https://api.github.com/users/mpermana","html_url":"https://github.com/mpermana","followers_url":"https://api.github.com/users/mpermana/followers","following_url":"https://api.github.com/users/mpermana/following{/other_user}","gists_url":"https://api.github.com/users/mpermana/gists{/gist_id}","starred_url":"https://api.github.com/users/mpermana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpermana/subscriptions","organizations_url":"https://api.github.com/users/mpermana/orgs","repos_url":"https://api.github.com/users/mpermana/repos","events_url":"https://api.github.com/users/mpermana/events{/privacy}","received_events_url":"https://api.github.com/users/mpermana/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":35,"created_at":"2015-10-06T05:34:34Z","updated_at":"2016-03-03T01:17:41Z","closed_at":"2015-10-14T09:20:39Z","pull_request":{"url":"https://api.github.com/repos/celery/celery/pulls/2840","html_url":"https://github.com/celery/celery/pull/2840","diff_url":"https://github.com/celery/celery/pull/2840.diff","patch_url":"https://github.com/celery/celery/pull/2840.patch"},"body":"https://github.com/celery/celery/issues/1628"},"comment":{"url":"https://api.github.com/repos/celery/celery/issues/comments/191524453","html_url":"https://github.com/celery/celery/pull/2840#issuecomment-191524453","issue_url":"https://api.github.com/repos/celery/celery/issues/2840","id":191524453,"user":{"login":"fillest","id":103396,"avatar_url":"https://avatars.githubusercontent.com/u/103396?v=3","gravatar_id":"","url":"https://api.github.com/users/fillest","html_url":"https://github.com/fillest","followers_url":"https://api.github.com/users/fillest/followers","following_url":"https://api.github.com/users/fillest/following{/other_user}","gists_url":"https://api.github.com/users/fillest/gists{/gist_id}","starred_url":"https://api.github.com/users/fillest/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fillest/subscriptions","organizations_url":"https://api.github.com/users/fillest/orgs","repos_url":"https://api.github.com/users/fillest/repos","events_url":"https://api.github.com/users/fillest/events{/privacy}","received_events_url":"https://api.github.com/users/fillest/received_events","type":"User","site_admin":false},"created_at":"2016-03-03T01:17:41Z","updated_at":"2016-03-03T01:17:41Z","body":"Ohh... So what's the state of this \"reject\" setting implementation? Can I just enable it or it doesn't work with auto-retrying (and is undocumented) yet? @tumb1er cau you please describe the issue more clearly one more time? Does it happen with some custom task handling?\r\n\r\nI think the current default behavior is nothing but expected when late_acks are enabled (which should have been enabled by default too but oh well, it's another story and at least it's configurable and clearly explained in the docs). The whole point of tuning for reliability (late_acks, auto-retrying, broker persistence and so on) is that in the real production environments a lot of bad things do happen and what is exactly expected is that task would be ack'ed _only_ when they clearly were processed, otherwise they will be retried if it is needed. If some task causes OOM-or-whatever-failure loop - I will have to deal with it but I will know that after it is dealt with, the system will automatically recover and continue to work and I won't have to manually fix nastier consistency issues.\r\nI think having this setting is very important - without it one has to build an extra layer of reliability system which is redundant because Celery already has a nice flexible supervisor component for task execution, and such a layer will be a supervisor for a supervisor, adding more complexity than if it were built-in."}}