It seemed to only affect some subdags (but I think even when restarted they
were still affected), it seemed like a race condition.

For the second question, we did not yet (but checking this is part of the
ticket).

On Tue, Mar 21, 2017 at 3:01 PM, Bolke de Bruin <[email protected]> wrote:

> @dan
>
> I'm obviously interested in the subdag issue as it is executed by the
> backfill logic. Do you have anything to reproduce it with? Can also talk
> about it tomorrow.
>
> Secondly, did you verify the all success / skipped 'fix' against 'wait for
> all tasks to finish'?
>
> @chris I also suggest using/embracing jira more (as you are doing), as it
> helps with cleaner changelogs, tracking and targeting releases.
>
> Also note that I already included some fixes in v1-8-test.
>
> Bolke
>
> Sent from my iPhone
>
> > On 21 Mar 2017, at 14:29, Ruslan Dautkhanov <[email protected]>
> wrote:
> >
> > Some of the issues I ran into while testing 1.8rc5 :
> >
> > https://issues.apache.org/jira/browse/AIRFLOW-1015
> >> https://issues.apache.org/jira/browse/AIRFLOW-1013
> >> https://issues.apache.org/jira/browse/AIRFLOW-1004
> >> https://issues.apache.org/jira/browse/AIRFLOW-1003
> >> https://issues.apache.org/jira/browse/AIRFLOW-1001
> >> https://issues.apache.org/jira/browse/AIRFLOW-1015
> >
> >
> > It would be great to have at least some of them fixed in 1.8.1.
> >
> > Thank you.
> >
> >
> >
> >
> > --
> > Ruslan Dautkhanov
> >
> > On Tue, Mar 21, 2017 at 3:02 PM, Dan Davydov <[email protected].
> invalid
> >> wrote:
> >
> >> Here is my list for targeted 1.8.1 fixes:
> >> https://issues.apache.org/jira/browse/AIRFLOW-982
> >> https://issues.apache.org/jira/browse/AIRFLOW-983
> >> https://issues.apache.org/jira/browse/AIRFLOW-1019 (and in general the
> >> slow
> >> startup time from this new logic of orphaned/reset task)
> >> https://issues.apache.org/jira/browse/AIRFLOW-1017 (which I will
> hopefully
> >> have a fix out for soon just finishing up tests)
> >>
> >> We are also hitting a new issue with subdags with rc5 that we weren't
> >> hitting with rc4 where subdags will occasionally just hang (had to roll
> >> back from rc5 to rc4), I'll try to spin up a JIRA for it soon which
> should
> >> be on the list too.
> >>
> >>
> >> On Tue, Mar 21, 2017 at 1:54 PM, Chris Riccomini <[email protected]
> >
> >> wrote:
> >>
> >>> Agreed. I'm looking for a list of checksums/JIRAs that we want in the
> >>> bugfix release.
> >>>
> >>> On Tue, Mar 21, 2017 at 12:54 PM, Bolke de Bruin <[email protected]>
> >>> wrote:
> >>>
> >>>>
> >>>>
> >>>>> On 21 Mar 2017, at 12:51, Bolke de Bruin <[email protected]> wrote:
> >>>>>
> >>>>> My suggestion, as we are using semantic versioning is:
> >>>>>
> >>>>> 1) no new features in the 1.8 branch
> >>>>> 2) only bug fixes in the 1.8 branch
> >>>>> 3) new features to land in 1.9
> >>>>>
> >>>>> This allows companies to
> >>>>
> >>>> Have a "known" version and can move to the new branch when they want
> to
> >>>> get new features. Obviously we only support N-1, so when 1.10 comes
> out
> >>> we
> >>>> stop supporting 1.8.X.
> >>>>
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>> On 21 Mar 2017, at 11:22, Chris Riccomini <[email protected]>
> >>>> wrote:
> >>>>>>
> >>>>>> Hey all,
> >>>>>>
> >>>>>> I suggest that we start a 1.8.1 Airflow release now. The goal would
> >>> be:
> >>>>>>
> >>>>>> 1) get a second release under our belt
> >>>>>> 2) patch known issues with the 1.8.0 release
> >>>>>>
> >>>>>> I'm happy to run it, but I saw Maxime mentioning that Airbnb might
> >>> want
> >>>> to.
> >>>>>> @Max et al, can you comment?
> >>>>>>
> >>>>>> Also, can folks supply JIRAs for stuff that think needs to be in the
> >>>> 1.8.1
> >>>>>> bugfix release?
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Chris
> >>>>
> >>>
> >>
>

Reply via email to