Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
From: Bolke de Bruin <bdbruin@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Experiences with 1.8.0
Date: Fri, 20 Jan 2017 23:55:02 +0100
References: <DA65F168-70DE-4ECC-BF7E-9D9DDCE091D2@gmail.com>
 <CABekQG6o+snHAHN3xkYz118OZn7CFHwo0Uax-pH1Yy2FYw2c7A@mail.gmail.com>
To: dev@airflow.incubator.apache.org
In-Reply-To: <CABekQG6o+snHAHN3xkYz118OZn7CFHwo0Uax-pH1Yy2FYw2c7A@mail.gmail.com>
Message-Id: <AAC5C755-EFD6-4D04-A28A-B89D4C2621AF@gmail.com>
archived-at: Fri, 20 Jan 2017 22:55:14 -0000

Will do. And thanks.

Adding another issue:=20

* Some of our DAGs are not getting scheduled for some unknown reason.
Need to investigate why.

Related but not root cause:
* Logging is so chatty that it gets really hard to find the real issue

Bolke.

> On 20 Jan 2017, at 23:45, Dan Davydov <dan.davydov@airbnb.com.INVALID> =
wrote:
>=20
> I'd be happy to lend a hand fixing these issues and hopefully some =
others
> are too. Do you mind creating jiras for these since you have the full
> context? I have created a JIRA for (1) and have assigned it to myself:
> https://issues.apache.org/jira/browse/AIRFLOW-780
>=20
> On Fri, Jan 20, 2017 at 1:01 AM, Bolke de Bruin <bdbruin@gmail.com> =
wrote:
>=20
>> This is to report back on some of the (early) experiences we have =
with
>> Airflow 1.8.0 (beta 1 at the moment):
>>=20
>> 1. The UI does not show faulty DAG, leading to confusion for =
developers.
>> When a faulty dag is placed in the dags folder the UI would report a
>> parsing error. Now it doesn=E2=80=99t due to the separate parising =
(but not
>> reporting back errors)
>>=20
>> 2. The hive hook sets =E2=80=98airflow.ctx.dag_id=E2=80=99 in hive
>> We run in a secure environment which requires this variable to be
>> whitelisted if it is modified (needs to be added to UPDATING.md)
>>=20
>> 3. DagRuns do not exist for certain tasks, but don=E2=80=99t get =
fixed
>> Log gets flooded without a suggestion what to do
>>=20
>> 4. At start up all running dag_runs are being checked, we seemed to =
have a
>> lot of =E2=80=9Cleft over=E2=80=9D dag_runs (couple of thousand)
>> - Checking was logged to INFO -> requires a fsync for every log =
message
>> making it very slow
>> - Checking would happen at every restart, but dag_runs=E2=80=99 =
states were not
>> being updated
>> - These dag_runs would never er be marked anything else than running =
for
>> some reason
>> -> Applied work around to update all dag_run in sql before a certain =
date
>> to -> finished
>> -> need to investigate why dag_runs did not get marked =
=E2=80=9Cfinished/failed=E2=80=9D
>>=20
>> 5. Our umask is set to 027
>>=20
>>=20