[
https://issues.apache.org/jira/browse/MAPREDUCE-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227856#comment-13227856
]
Jason Lowe commented on MAPREDUCE-3928:
---------------------------------------
Yes, I think the confusion here is that a user is primarily interested in
whether their job succeeded, failed, was killed, etc. The filter links on the
apps page implies one can quickly filter the apps to one of those states, yet
apps that have failed or killed often don't show up under the FAILED or KILLED
filters. It's not clear on the web page that those only filter State instead
of the FinalState, and many users may not understand or appreciate the
distinction between State and FinalState (at least for MapReduce apps).
For example, it can be a bit confusing why a job that's killed via mapred job
-kill shows up as KILLED / KILLED, while another job where the AM process is
killed directly is listed as FINISHED / KILLED.
> App GUI Cluster->Applications UI has confusing job status report
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-3928
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3928
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 0.23.1
> Reporter: patrick white
>
> The 0.23.1 Application GUI has some potential usability issues and confusion
> points with respect to job status, from a user's perspective.
> Currently, when starting from the App UI base link of
> http://<RM_HOST>:8088/cluster, the main window shows "All Applications", and
> in
> the upper left corner is the "Cluster" pulldown, opened up showing the
> following list:
> About
> Nodes
> Applications
> - New
> - Submitted
> - Accepted
> - Running
> - Finished
> - Failed
> - Killed
> Scheduler
> When jobs are submitted, they show up in the pre-final states, like Accepted
> and Running. however after completion, no matter on the final outcome of a job
> (SUCCESS, KILLED or FAILED), all jobs are listed under FINISHED, this is okay
> since any completion result qualifies as Finished, but the FAILED and KILLED
> jobs do not appear in the corresponding links for FAILED or KILLED.
> Clicking on FAILED or KILLED reports "No data available in table", even with
> Failed or Killed jobs showing up in the FINISHED link. This can be very
> confusing to a user checking on their jobs, especially for someone using the
> direct URL links, such as:
> http://<RM_HOST>:8088/cluster/apps/FAILED
> http://<RM_HOST>:8088/cluster/apps/KILLED
> Another potential issue is that the RM and AM each have their own
> interpretation of a job's result, so the State and FinalStatus reported in the
> Cluster Metrics display may not align with the defined states in the Cluster
> pulldown. It would be useful to clearly delineate areas of the GUI wrt the
> component visible states of a user's job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
