Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0CFAF200CDA for ; Fri, 4 Aug 2017 19:22:02 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0B42916DF59; Fri, 4 Aug 2017 17:22:02 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4F7B416DF55 for ; Fri, 4 Aug 2017 19:22:01 +0200 (CEST) Received: (qmail 69409 invoked by uid 500); 4 Aug 2017 17:21:55 -0000 Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list dev@airflow.incubator.apache.org Received: (qmail 69353 invoked by uid 99); 4 Aug 2017 17:21:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2017 17:21:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id AD695C00E7 for ; Fri, 4 Aug 2017 17:21:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=cloverhealth.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id L0dhzQmbErkE for ; Fri, 4 Aug 2017 17:21:52 +0000 (UTC) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 33BA35F5B4 for ; Fri, 4 Aug 2017 17:21:52 +0000 (UTC) Received: by mail-oi0-f41.google.com with SMTP id d71so20930091oih.0 for ; Fri, 04 Aug 2017 10:21:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=fep8tOKpbGyH/bH7GrjW1M2W9UViMW5b0bEBeqiR8EE=; b=SS4+Zyc12FLrvsDnWUl4wf19UPCGWd1os4Ehdc35uy2MmsDnVB0r91b3dg9/8r/r0h QUP2YPHKmdxEqHT0xluX5ec5RMSLNJDamMENioYmVoQPIsBtt0QaSnOIFRWk7pt/kV3D Ce7mqNqqEk7UKpABEqPObho4uSCtjiJ0Bp79MYvboId3OSniMhyR0zTzT2RgmOyJrZr4 ZS4TWrohUIS8xqIXwBfHVS/ADUAYCYa7MBOCVfJh03YnhixRS0E3AOEcWgoZqF07Z/L6 mzn985j+C2i4DH4iaxjFP+WFFgtXFmEwZWyiIHkbvHma7Zc2J0wcRu35ShNyjYafliyR g2lw== X-Gm-Message-State: AHYfb5hC7CZzfxbrnYwboRZActGVctQ/ZfJGqO/mni8lfZSi5tEM3pgh 5doVVM0KmcXgB05/ixqVLAJqZy6nUsTiZWU= X-Received: by 10.202.236.3 with SMTP id k3mr2071509oih.20.1501867310432; Fri, 04 Aug 2017 10:21:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: George Leslie-Waksman Date: Fri, 04 Aug 2017 17:21:39 +0000 Message-ID: Subject: Re: Tasks stay queued when they fail in celery To: dev@airflow.incubator.apache.org Content-Type: multipart/alternative; boundary="001a1134e9a089e7500555f0bb42" archived-at: Fri, 04 Aug 2017 17:22:02 -0000 --001a1134e9a089e7500555f0bb42 Content-Type: text/plain; charset="UTF-8" We've seen this before as well, it's a bug in the Celery Executor that has a bunch of different manifestations. There is at least one open issue relating to this bug: https://issues.apache.org/jira/browse/AIRFLOW-1463 I have been working on a fix but it's likely to be a few more days before I have a chance to make some progress. --George On Fri, Jul 28, 2017 at 5:05 PM David Capwell wrote: > We noticed that in the past few days we keep seeing tasks stay in the > queued state. Looking into celery, we see that the task had failed. > > Traceback (most recent call last): > File "/python/lib/python2.7/site-packages/celery/app/trace.py", line > 367, in trace_task > R = retval = fun(*args, **kwargs) > File "/python/lib/python2.7/site-packages/celery/app/trace.py", line > 622, in __protected_call__ > return self.run(*args, **kwargs) > File > "/python/lib/python2.7/site-packages/airflow/executors/celery_executor.py", > line 59, in execute_command > raise AirflowException('Celery command failed') > AirflowException: Celery command failed > > > Why does airflow not learn about this and recover? And what can we do to > prevent this? > > Thanks for your time reading this email. > --001a1134e9a089e7500555f0bb42--