As Gopal mentioned, it is optional. The log message could probably be set to a WARN to not confuse users.
— Hitesh On Feb 25, 2016, at 7:26 AM, Stephen Sprague <sprag...@gmail.com> wrote: > hey guys, > still not getting jobs to the running state via tez->beeline->hs2. > > lemme ask this first: Is is mandatory that the Tez UI be up an running for > this to work? > > this looks to be a hard error (see below) but given the "local cli" works i > don't think its *mandatory*. But maybe via HS2 it is? > > from yarn logs: > 2016-02-25 07:07:56,744 [ERROR] [main] |web.WebUIService|: Tez UI History URL > is not set > > Thanks, > Stephen > PS setting up the web service is just another step and complication i'm > hoping to avoid for just testing. :) > > On Mon, Feb 22, 2016 at 10:43 AM, Bikas Saha <bi...@apache.org> wrote: > Hi Stephen, > > > > Thanks for bearing with any delays on our side and keeping us updated. In the > end if we figure out that this is less about bugs in Tez/Hive and more about > lack of well documented best practices, then it would be useful to produce a > wiki page about this. > > > > Thanks > > Bikas > > > > From: Stephen Sprague [mailto:sprag...@gmail.com] > Sent: Monday, February 22, 2016 6:59 AM > To: user@tez.apache.org > Subject: Re: tez and beeline and hs2 > > > > just an update. i haven't given up! i've just been pulled into other things > this weekend and am hoping to pick it up again this week. > > > > On Fri, Feb 19, 2016 at 9:30 AM, Hitesh Shah <hit...@apache.org> wrote: > > Not exactly. I think the UI bits might be a red-herring. Bouncing YARN and > HS2 also should unlikely be needed unless you are modifying configs. > > There is likely a bug ( the NPE being logged ) in the shutting down code for > the org.apache.tez.dag.history.logging.impl.SimpleHistoryLoggingService ( if > it was not started properly ) but the fact that it is shutting down means > that there is something else wrong ( which should have happened before the > shutdown sequence kicked in ). Feel free to file a bug with the logs attached > if you cannot attach them over the mailing list here. > > thanks > — Hitesh > > > > On Feb 19, 2016, at 7:16 AM, Stephen Sprague <sprag...@gmail.com> wrote: > > > Hi Gopal, > > nice. I should have known that command as you and Hitesh have given that > > advice in the past on various threads here! sorry for that. > > > > And sure enough the smoking gun reveals itself. thank you. > > > > {quote} > > 2016-02-18 18:40:19,672 [ERROR] [main] |web.WebUIService|: Tez UI History > > URL is not set > > 2016-02-18 18:40:19,731 [WARN] > > [ServiceThread:org.apache.tez.dag.history.HistoryEventHandler] > > |service.AbstractService|: When stopping the service > > org.apache.tez.dag.history.logging.impl.SimpleHistoryLoggingService : > > java.lang.NullPointerException > > java.lang.NullPointerException > > {quote} > > > > So it looks like this Tez UI app is required for 'jdbc' mode. Lemme > > research that puppy and perhaps bounce Yarn and HS2. > > > > Thanks again for shining the light! > > > > Cheeers, > > Stephen. > > > > On Thu, Feb 18, 2016 at 10:09 PM, Gopal Vijayaraghavan <gop...@apache.org> > > wrote: > > > > > > > >http://dwrdevnn1.sv2.trulia.com:8088/proxy/application_1455811467110_0307/ > > > > > ><http://dwrdevnn1.sv2.trulia.com:8088/proxy/application_1455811467110_0307 > > >/> > > ... > > > So my question is whatya suppose is causing this? I'm pretty darn sure > > >the classpath is legit now. > > > > Two steps forward, one step back :) > > > > yarn logs -applicationId application_1455811467110_0307 for answers. > > > > Cheers, > > Gopal > > > > > > > > > >
