[
https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087906#comment-13087906
]
Robert Joseph Evans commented on HADOOP-7532:
---------------------------------------------
bq. Yes. see my response in MAPREDUCE-2858 for reasons.
I read the comment in MAPREDUCE-2858 before writing my previous comment. You
want to be able to run different versions of the UI at the same time. That is
great, but I argue is not worth the development effort at this time to support
it, and there are more standard ways to support bucket testing of different UIs
on a trusted server then trying to launch a separate web server for each
application that is running. I am not suggesting that we set up a trusted
server for each and every version/user. That is not scalable. What I am
saying is provide a simple GUI that uses the client APIs to pull the data back.
bq. you can't just link to an arbitrary webapp in RM app list
I agree completely I don't feel secure linking to an arbitrary webapp whether
it is running on a gateway or is running as part of an application master. If
it is controlled completely by an arbitrary user it is essentially impossible
to strip out all potentially malicious content in HTML/javascript. That is why
the RM app would link to this basic GUI on a trusted server running trusted
code.
bq. It's an operations nightmare to let users to run arbitrary web UI on a
gateway
That is probably true, and is great argument to get a webservice up and running
so the enhanced visualizations/analytics could all be done on the users desktop
:).
bq. In any case, per user/version web UI is a major step forward, just like per
user/version mapreduce runtime in MRv2.
I disagree I think most users will not want to take the time to update the GUI
or try out new/interesting visualizations. What most of the users I have
talked to want is access to the data about their processes. They want to do
advanced analysis themselves that is accessible outside of the GUI for a single
MR job. This is so they can do their own monitoring and alerting. This is so
they can analyze the trends in all their processes not just the ones that are
currently running and try to understand what they can do to be more efficient.
MRv2 opens up the door to a set of developers to create new and interesting
ways, including 1 off solutions to process data and solve problems. I am just
not convinced that any of their problems really involve the Application Master
GUI.
bq. IMO, the current MR history server is the ideal candidate for data and UI
separation/refactor.
ditto.
> Hadoop web UI 2.0
> -----------------
>
> Key: HADOOP-7532
> URL: https://issues.apache.org/jira/browse/HADOOP-7532
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.23.0
> Reporter: Luke Lu
> Assignee: Luke Lu
> Fix For: 0.23.0
>
>
> People have expressed interests of bringing Hadoop web UI up to date with the
> lightweight embedded web mvc framework used in MAPREDUCE-279 (cf.
> MAPREDUCE-2399). This is the umbrella jira for UI improvement for 0.23+.
> Individual items like web framework refactor/move and the unique challenge
> for MR2 webapp security will be filed separately.
> Thoughts/ideas on various improvement of Hadoop web UI are welcome here. Some
> of the ideas will naturally become sub-issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
