Thanks Yadong, I think one of the purpose to find the failed attempts is that we want to look into the logs in the failed node (node may change across attempts). However, from the POC, I didn't find a log link on each attempts. Maybe we can add such feature?
Best, Jark On Fri, 21 Feb 2020 at 11:51, Kurt Young <ykt...@gmail.com> wrote: > Hi Yadong, > > Thanks for the proposal, it's a useful feature, especially for batch jobs. > But according > to the examples you gave, I can't tell whether i got required information > from that. > Can you replace the demo job to a more complex batch job and then we can > see some > differences of start/stop time of different tasks and attempts? > > Best, > Kurt > > > On Thu, Feb 20, 2020 at 5:46 PM Yadong Xie <vthink...@gmail.com> wrote: > > > Hi all > > > > I want to start the vote for FLIP-100, which proposes to add attempt > > information inside subtask and timeline in web UI. > > > > To help everyone better understand the proposal, we spent some efforts on > > making an online POC > > > > Timeline Attempt (click the vertex timeline to see the differences): > > previous web: > > > http://101.132.122.69:8081/#/job/9d651769488466d33e7a607e85203543/timeline > > POC web: > > > > > http://101.132.122.69:8081/web/#/job/9d651769488466d33e7a607e85203543/timeline > > > > Subtask Attempt (click the vertex and switch to subtask tab to see the > > differences): > > previous web: > > > http://101.132.122.69:8081/#/job/9d651769488466d33e7a607e85203543/overview > > POC web: > > > > > http://101.132.122.69:8081/web/#/job/9d651769488466d33e7a607e85203543/overview > > > > > > The vote will last for at least 72 hours, following the consensus voting > > process. > > > > FLIP wiki: > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-100%3A+Add+Attempt+Information > > > > Discussion thread: > > > > > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-75-Flink-Web-UI-Improvement-Proposal-td33540.html > > > > Thanks, > > > > Yadong > > >
