Thanks Taylor, We are getting this issue even after restart. We are observing that task instance state is transitioned from scheduled->queued->up_for_retry and dag gets stuck in up_for_retry state. Behind the scenes executor keep on retrying the dag's task exceeding the max retry limit. In normal scenario task state should have following transition scheduled->queued->running->up_for_retry but we are seeing task is not entered in to running state rather it moves directly to up_for_retry from queued state. Any pointer on this would be helpful.
Thanks, raman Gupta On 2018/08/16 16:05:31, Taylor Edmiston <tedmis...@gmail.com> wrote: > Does a scheduler restart make a difference? > > *Taylor Edmiston* > Blog <https://blog.tedmiston.com/> | CV > <https://stackoverflow.com/cv/taylor> | LinkedIn > <https://www.linkedin.com/in/tedmiston/> | AngelList > <https://angel.co/taylor> | Stack Overflow > <https://stackoverflow.com/users/149428/taylor-edmiston> > > > On Thu, Aug 16, 2018 at 4:25 AM, ramandu...@gmail.com <ramandu...@gmail.com> > wrote: > > > Hi All, > > > > We are using airflow 1.9 with Local Executor more. Intermittently we are > > observing that tasks are getting stuck in "up_for_retry" mode and are > > getting retried again and again exceeding their configured max retries > > count. like we have configured max retries as 2 but task is retried 15 > > times and got stuck in up_for_retry state. > > Any pointer on this would be helpful. > > > > Thanks, > > Raman Gupta > > >
