Hello Xiaoyong,

Could you shed more light on the problems you have been encountering ( and with 
which version of the hadoop )? Some of the details on how to use YARN timeline 
are documented here: http://tez.apache.org/tez_yarn_timeline.html - let me know 
if that helps. 
Let us also know what version of Tez you are trying and we can guide you 
further. 

Beyond that, assuming you manage to get Tez to write data correctly to YARN 
timeline, the UI as you mentioned is JS based but it is built on top of the 
YARN timeline web services. There is some initial info on how to setup the UI 
here:
https://github.com/apache/tez/blob/master/tez-ui/README.TXT. If you face any 
issues using the instructions, please do let us know as this will get refined 
as we get closer to the 0.6 release in the next few weeks. 

Some of the web service calls can be found in 
app/scripts/models/TimelineRestAdapter.js.

For the most part, all the data is retrieved via these endpoints: 

<TIMELINEHOST:PORT>/ws/v1/timeline/TEZ_APPLICATION
<TIMELINEHOST:PORT>/ws/v1/timeline/TEZ_DAG_ID
<TIMELINEHOST:PORT>/ws/v1/timeline/TEZ_VERTEX_ID
<TIMELINEHOST:PORT>/ws/v1/timeline/TEZ_TASK_ID
<TIMELINEHOST:PORT>/ws/v1/timeline/TEZ_TASK_ATTEMPT_ID

( timeline usually runs on port 8188 by default )

thanks
— Hitesh  


On Dec 12, 2014, at 2:21 AM, Xiaoyong Zhu <xiaoy...@microsoft.com> wrote:

> Hi Tez experts
>  
> I am really excited to see the Tez UI will be coming out in 0.6! it’s really 
> helpful!
> I want to try that in my local sandbox (Cloudera/Hortonworks) but I 
> encountered a lot of issues (such as cannot find 
> org.apache.tez.dag.history.logging.ats packages) and I decide to give up 
> building it myself. Is this feature available in Tez 0.5 releases so I could 
> download the bits and deploy rather than build from scratch?
>  
> Another question is that, I know it is a JS build atop of a bunch of RESTful 
> APIs after talking with Gopal – could someone guide me where is the REST API 
> documentation? I want to have a look at the REST API abilities.
>  
> Thanks!
>  
> Xiaoyong

Reply via email to