Hi Kurt, The Tez UI as documented should work with any version beyond 0.5.2 if the history logging is configured to use YARN timeline. As for scopes, some bits of the vertex description are currently not displayed in the UI though I am not sure if Pig has integrated with that API yet. Depending on the version of hadoop you are running and the scale at which you are running, there are some known issues with the YARN timeline impl from a scalability perspective but the Yahoo folks have implemented some fixes/config workarounds to get around those. @Jon Eagles, any chance of publishing a wiki for the configs that you recommend running with for YARN Timeline with the level db impl? ( and also the HDFS based impl though that this is not really available in any hadoop release as of now ).
If you are trying out the UI, it would be good if you also try out tez-ui2 as it has some enhancements coming down the pipe such as a vertex swim lane which provides a better overall view of the vertices and how they progress/time they took. The UI2 version is fairly new so feedback will be highly appreciated. @Rohini, has Pig started setting the vertex info? @Sreenath, do we have an open jira for the vertex description to be displayed in the UI? thanks — Hitesh On Apr 5, 2016, at 11:04 AM, Kurt Muehlner <kmuehl...@connexity.com> wrote: > I have a question about the availability of the Tez web UI in Pig on Tez. > The Pig ‘Performance and Efficiency’ doc states, "Tez specific GUI is not > available yet, there is no GUI to track task progress. However, log message > is available in GUI.” What does this mean, precisely? We have not deployed > and configured the Tez UI described here: > https://tez.apache.org/tez-ui.html. Will that UI work when running Tez on > Pig? If so, what does ‘Tez specific GUI is not available yet’ mean? > > What I am most specifically concerned about is the ability to see which Pig > aliases are being assigned to which Tez vertices, or failing that, which Pig > aliases are being processed by a particular Tez DAG. This is currently not > available in logs in pig 0.15.0, although I’m aware it is in master. > > What are best practices for Pig 0.15.0? > > Thanks, > Kurt
