Awesome - thank you for the help. Does this have anything to do with the default 1h visibility timeout when using redis as a broker? Have been doing some more digging, and was not aware of this caveat - however, am not sure if this behavior is what leads to the symptoms I am seeing (as well as what is documented in the bug report)…
Thanks again for the help - much appreciated! Cheers, J > On Jul 16, 2017, at 3:22 AM, Alex Guziel <[email protected]> > wrote: > > I think this may be related to a celery bug. I'll follow up with more > details later. > > On Sun, Jul 16, 2017 at 12:56 AM Jawahar Panchal <[email protected]> > wrote: > >> Hi! >> >> I am currently running a couple of long-running tasks on a >> database/dataset at school for a project that results in behavior/log >> output similar to what was flagged in this bug: >> https://issues.apache.org/jira/browse/AIRFLOW-1258 < >> https://issues.apache.org/jira/browse/AIRFLOW-1258> >> >> Wasn’t sure if anyone on the list had seen anything similar, or would know >> what I can do to possibly debug further/patch. As it takes 1hr to test a >> change, needless to say any pointers from the dev team on the right >> direction to look within the codebase would be much appreciated! :) >> >> Thanks in advance for everyone’s/anyone's time and help - am not an >> Airflow expert, but am hopefully learning quickly enough to help resolve >> this issue (if I am ‘barking up the right tree’ with this bug number…) >> >> Cheers, >> J >> >>
