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 A6AB4200BB3 for ; Wed, 2 Nov 2016 16:07:39 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A5585160AFB; Wed, 2 Nov 2016 15:07:39 +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 EAF0A160AEA for ; Wed, 2 Nov 2016 16:07:38 +0100 (CET) Received: (qmail 88456 invoked by uid 500); 2 Nov 2016 15:07:37 -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 88435 invoked by uid 99); 2 Nov 2016 15:07:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2016 15:07:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E59B51A7C20 for ; Wed, 2 Nov 2016 15:07:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 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, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=blueapron.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YW62bGDtSNX7 for ; Wed, 2 Nov 2016 15:07:34 +0000 (UTC) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3309C5FC1C for ; Wed, 2 Nov 2016 15:07:33 +0000 (UTC) Received: by mail-lf0-f43.google.com with SMTP id c13so15380521lfg.0 for ; Wed, 02 Nov 2016 08:07:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=JAkaaN2wc2WbVqUa4j6hsqXkkzlO3lRSiLCFWdBut5g=; b=UJWVegz5iulcSRpn7JF4qFwxSNxlSKfTIY9TG0iB4YtlYHMgvRJVqhgGM5pESs+41+ GehQcpnavEASn2Dr18o2ZcoryVGFiWzlux5WN473XxqXnPHvSvX7QTcJBbk+LHaw24t4 F/ajpoCzlUtxaFvknqQ0XTaNfguxRKlu1XNdU6bovfErf3VQZ4QJrc5Ry0YR1J/nUDqT Vi0E/NxbTaS+okbcqApRYAw6m4s6iUSNNbv/x/XYM0nWoKU+vtXmI5Sq/p2S2k0ZHn5t agtBBf6mmv4Q+BRNCmJQtFjRSevhxYtH0nIFnI1Xji43FO36jJ9PGWU5Fy/wtQz9cM9l jsow== X-Gm-Message-State: ABUngvfTvvD7xKavhdg+fOekNX66WFwpwnHs6vrkRP3Tw6KT4ABG8/x32YAuvMPIa8cns+XXGkXQbSBy55mQH0Jv X-Received: by 10.25.24.98 with SMTP id o95mr2353692lfi.4.1478099236505; Wed, 02 Nov 2016 08:07:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.99.73 with HTTP; Wed, 2 Nov 2016 08:07:15 -0700 (PDT) In-Reply-To: References: From: Joseph Napolitano Date: Wed, 2 Nov 2016 11:07:15 -0400 Message-ID: Subject: Re: Airflow state change diagram To: dev@airflow.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11401936ef680e054052cb21 archived-at: Wed, 02 Nov 2016 15:07:39 -0000 --001a11401936ef680e054052cb21 Content-Type: text/plain; charset=UTF-8 Gerard, This is great. Thanks for sharing this. Joe On Wed, Nov 2, 2016 at 7:43 AM, twinkle sachdeva wrote: > Thanks Gerard for sharing it. > > Regards, > Twinkle > > On Mon, Oct 31, 2016 at 2:35 AM, Gerard Toonstra > wrote: > > > I was looking at trying to fix AIRFLOW-137 (max_active_runs not > respected), > > but quickly noticed that the code that does all the scheduling is rather > > complex with state updates going on across multiple source files in > > multiple threads, etc. > > > > It's then best to find a suitable way to visualize all this complexity, > so > > I built this state change diagram: > > > > https://docs.google.com/spreadsheets/d/1vVvOwfDSacTC_ > YzwUkOMyykP6LiipCeoW_ > > V70PuFrN4/edit?usp=sharing > > > > The state changes represent a potential execution path where the state > for > > a task instance will be updated to that value. Backfill is not considered > > in this diagram. States for dagruns/jobs/dags are also not considered. > > > > Could be useful for someone else. > > > > Rgds, > > > > Gerard > > > -- *Joe Napolitano *| Sr. Data Engineer www.blueapron.com | 5 Crosby Street, New York, NY 10013 --001a11401936ef680e054052cb21--