[ 
https://issues.apache.org/jira/browse/HAMA-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061947#comment-14061947
 ] 

Edward J. Yoon commented on HAMA-910:
-------------------------------------

Another suggestion is that it would be nice if we can browse the failed or 
other task's log via Web UI.

For example, we can see the Job status by clicking the Jobid link at 
http://edward-virtualbox:40013/bspjob.jsp?jobid=job_201407151936_0001

This page currently provides the "Job Log viewer" link but it only browses a 
master server's Log folder. If the task of Job is not assigned to master 
server, this link will be broken.

To solve this problem, I think, JobStatus should have to provide the list of 
assigned tasks' hostname.

> Web UI Improvement 
> -------------------
>
>                 Key: HAMA-910
>                 URL: https://issues.apache.org/jira/browse/HAMA-910
>             Project: Hama
>          Issue Type: Improvement
>          Components: web UI
>    Affects Versions: 0.7.0
>            Reporter: Victor Lee
>            Assignee: Victor Lee
>             Fix For: 0.7.0
>
>         Attachments: HAMA-910-v2.patch, HAMA-910-v3.patch, HAMA-910.patch, 
> [v3]bspmaster.png, bspmaster.png, config.png, logdetail.png, loglist.png, 
> logtail.png, tasklogs.png
>
>
> I think function in the Web UI is not enough. 
> It is inconvenient to check the log file. 
> Further, they seem to come in handy when there is the ability to display the 
> configuration information 
> I want to improve the following functions.
> ----
> [Web UI(manager) improvement]
> . configure System(Hama)

> - Displays Hama Configuration

> - System Information (Displays various environmental information to assist 
> trouble-shooting)
> . System Log
- Server log (BSP, Zookeeper, Groom Server)

> - Displays, download, tail log etc ..
> . Node Information
 - inform the various hama node.
> . Statistics
 - Check hama's resource utilizations and..
> and.. I am interested in this improvement ; )



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to