We tried it and it works that v2.0 History Server can read the v1.6 logs. Note that the UI has a regression. When there are too many jobs, the UI will freeze because the new code tries to cache everything. We submitted a JIRA: https://issues.apache.org/jira/browse/SPARK-17243
On Thu, Sep 15, 2016 at 11:08 AM, Mario Ds Briggs <mario.bri...@in.ibm.com> wrote: > I had checked in 1.6.2 and it doesnt. I didnt check in lower versions. The > history server logs do show a 'Replaying log path: file:xxx.inprogress' > when the file is changed , but a refresh on UI doesnt show the new > jobs/stages/tasks whatever > > > > thanks > Mario > > [image: Inactive hide details for Ryan Williams ---15/09/2016 11:19:56 > pm---What is meant by: """]Ryan Williams ---15/09/2016 11:19:56 pm---What > is meant by: """ > > From: Ryan Williams <ryan.blake.willi...@gmail.com> > To: Reynold Xin <r...@databricks.com>, Mario Ds Briggs/India/IBM@IBMIN > Cc: "dev@spark.apache.org" <dev@spark.apache.org> > Date: 15/09/2016 11:19 pm > Subject: Re: Compatibility of 1.6 spark.eventLog with a 2.0 History Server > ------------------------------ > > > > What is meant by: > > """ > (This is because clicking the refresh button in browser, updates the UI > with latest events, where-as in the 1.6 code base, this does not happen) > """ > > Hasn't refreshing the page updated all the information in the UI through > the 1.x line? > > >
