{"action":"opened","issue":{"url":"https://api.github.com/repos/celery/celery/issues/2891","labels_url":"https://api.github.com/repos/celery/celery/issues/2891/labels{/name}","comments_url":"https://api.github.com/repos/celery/celery/issues/2891/comments","events_url":"https://api.github.com/repos/celery/celery/issues/2891/events","html_url":"https://github.com/celery/celery/issues/2891","id":113598382,"number":2891,"title":"Is Celery threadsafe?","user":{"login":"piotrmaslanka","id":103189,"avatar_url":"https://avatars.githubusercontent.com/u/103189?v=3","gravatar_id":"","url":"https://api.github.com/users/piotrmaslanka","html_url":"https://github.com/piotrmaslanka","followers_url":"https://api.github.com/users/piotrmaslanka/followers","following_url":"https://api.github.com/users/piotrmaslanka/following{/other_user}","gists_url":"https://api.github.com/users/piotrmaslanka/gists{/gist_id}","starred_url":"https://api.github.com/users/piotrmaslanka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/piotrmaslanka/subscriptions","organizations_url":"https://api.github.com/users/piotrmaslanka/orgs","repos_url":"https://api.github.com/users/piotrmaslanka/repos","events_url":"https://api.github.com/users/piotrmaslanka/events{/privacy}","received_events_url":"https://api.github.com/users/piotrmaslanka/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-27T14:37:14Z","updated_at":"2015-10-27T14:37:14Z","closed_at":null,"body":"Having encountered a hazard in #2869, I examined some other Celery backends. None of them shows particular thought in being thread-safe.\r\n\r\nThis raises an open question - is Celery internally thread-safe enough to warrant supporting threadpool? I know this is a borderline use case, but I think it's better to deprecate threadpool backend than risk users enabling it and getting blown up on race conditions."}}