TEZ UI Issues (master)

[Jeff Zhang <zj...@gmail.com>]

Hi all,

I run the tez-ui of master, and found couple of issues. Here's my
environment.

OS: Mac OS 10.9
Chrome
Tez master branch

*1.  DAG Diagram View.*
      - Is it possible to make the mouse as hand shape to indicate that
user can move the diagram.
      - Does it make more sense to put Edge Source Class before Edge
Destination Class
[image: Inline image 1]
      - Sometimes the vertex info is too small that the right side info is
cut off
[image: Inline image 2]
     - The DAG diagram box is too small for complicated DAG, although I can
zoom in, but there's enough space to enlarge the diagram box.

     -  The vertex group is not clear. As least it should tell that
scope-37 is the vertex group name in the following screenshot.  There's one
jira for visualize vertex group as sub graph (TEZ-1972) , maybe tez-ui can
use the same way to make the vertex group much clear

    [image: Inline image 3]



* 2. Topological order of vertex and order of task/taskattempt*
        -  We could sort the vertex by its id, the vertices have been
sorted in topological order when converting to DAGPlan
        -  Task & TaskAttempt  also can be sorted by its id. Currently the
last started task/taskattempt is on the top.

* 3. Display issue of Task Panel*
        The default number of showing task is 10, I have a dag with more
than 10 tasks. I change the number of rows to 25, it doesn't show 25 tasks.
I have to refresh page to make it work.

* 4.  Recovery case issue*

         - Task status may not be available due to lost of
TaskFinishedEvent (TEZ-2024)

          [image: Inline image 4]

        - StartTime of Task is lost. It is because RecoveryService and
ATSHistoryLoggingService
are in different threads. The TaskStartedEvent may have been logged in
RecoveryService while it hasn't been put to TimelineService in
ATSHistoryLoggingService.

[image: Inline image 6]


        - Last application_attempt's task attempt info is lost in swimlane
in recovery. Not sure what kind of data swimlane use, but looks like it due
to AMContainerImpl is not recovered. (TEZ-860)


[image: Inline image 5]

Task order

Task Attempt Order

-- 
Best Regards

Jeff Zhang

Re: TEZ UI Issues (master)

[Hitesh Shah <hi...@apache.org>]

Hello Jeff, 

Thanks for trying out the UI. Can you file JIRAs for these improvements and set the component to UI so that folks like Sreenath and other 
folks who are interesting in working on the UI can easily find them? 

thanks
— Hitesh



On Feb 3, 2015, at 2:33 AM, Jeff Zhang <zj...@gmail.com> wrote:

> Hi all,
> 
> I run the tez-ui of master, and found couple of issues. Here's my environment.
> 
> OS: Mac OS 10.9
> Chrome
> Tez master branch
> 
> 1.  DAG Diagram View.
>       - Is it possible to make the mouse as hand shape to indicate that user can move the diagram.
>       - Does it make more sense to put Edge Source Class before Edge Destination Class
> 
>       - Sometimes the vertex info is too small that the right side info is cut off
> 
>      - The DAG diagram box is too small for complicated DAG, although I can zoom in, but there's enough space to enlarge the diagram box.
> 
>      -  The vertex group is not clear. As least it should tell that scope-37 is the vertex group name in the following screenshot.  There's one jira for visualize vertex group as sub graph (TEZ-1972) , maybe tez-ui can use the same way to make the vertex group much clear
> 
>     
> 
> 
> 
>  2. Topological order of vertex and order of task/taskattempt
>         -  We could sort the vertex by its id, the vertices have been sorted in topological order when converting to DAGPlan
>         -  Task & TaskAttempt  also can be sorted by its id. Currently the last started task/taskattempt is on the top.
> 
>  3. Display issue of Task Panel
>         The default number of showing task is 10, I have a dag with more than 10 tasks. I change the number of rows to 25, it doesn't show 25 tasks. I have to refresh page to make it work.
> 
>  4.  Recovery case issue
>          - Task status may not be available due to lost of TaskFinishedEvent (TEZ-2024)
>           
>         - StartTime of Task is lost. It is because RecoveryService and ATSHistoryLoggingService are in different threads. The TaskStartedEvent may have been logged in RecoveryService while it hasn't been put to TimelineService in ATSHistoryLoggingService.
> 
> 
>         - Last application_attempt's task attempt info is lost in swimlane in recovery. Not sure what kind of data swimlane use, but looks like it due to AMContainerImpl is not recovered. (TEZ-860)
> 
> 
> Task order
> Task Attempt Order
> 
> -- 
> Best Regards
> 
> Jeff Zhang