Hi Julio, Yes, it seems that fifty-five minutes is really long. However, it is linear with the time and size of the previous task adjacent to it in the diagram. I think your real application is concerned about why Flink accesses HDFS so slowly. You can call the DEBUG log to see if you can find any clues, or post the log to the mailing list to help others analyze the problem for you.
Thanks, vino. Julio Biason <julio.bia...@azion.com> 于2018年9月15日周六 上午7:03写道： > (Just an addendum: Although it's not a huge problem -- we can always > increase the checkpoint timeout time -- this anomalous situation makes me > think there is something wrong in our pipeline or in our cluster, and that > is what is making the checkpoint creation go crazy.) > > On Fri, Sep 14, 2018 at 8:00 PM, Julio Biason <julio.bia...@azion.com> > wrote: > >> Hey guys, >> >> On our pipeline, we have a single slot that it's taking longer to create >> the checkpoint compared to other slots and we are wondering what could be >> causing it. >> >> The operator in question is the window metric -- the only element in the >> pipeline that actually uses the state. While the other slots take 7 mins to >> create the checkpoint, this one -- and only this one -- takes 55mins. >> >> Is there something I should look at to understand what's going on? >> >> (We are storing all checkpoints in HDFS, in case that helps.) >> >> -- >> *Julio Biason*, Sofware Engineer >> *AZION* | Deliver. Accelerate. Protect. >> Office: +55 51 3083 8101 <callto:+555130838101> | Mobile: +55 51 >> <callto:+5551996209291>*99907 0554* >> > > > > -- > *Julio Biason*, Sofware Engineer > *AZION* | Deliver. Accelerate. Protect. > Office: +55 51 3083 8101 <callto:+555130838101> | Mobile: +55 51 > <callto:+5551996209291>*99907 0554* >
