[
https://issues.apache.org/jira/browse/HADOOP-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089878#comment-13089878
]
Luke Lu commented on HADOOP-7532:
---------------------------------
First some historical perspective: I have actually proposed the WS + trusted
webapp as an option, when I originally architected AM webapps 8 months ago. The
people following the discussion at the time picked the current option. In
retrospect, I think the current option is more in line with the spirit of MRv2.
bq. That is great, but I argue is not worth the development effort at this time
to support it.
The development effort to support generic AM webapp security is optional and
incremental and has much lower cost than re-architect the whole thing, period.
bq. 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.
We're not talking about bucket testing here. We're talking about a major
benefit of MRv2: allowing different organizations to move to different versions
of different *types* of apps on their own schedule. We're not talking about
just mapreduce, which is just one *type* of apps. The WS+trusted UI approach
requires O(T*V) (T = number of types of apps, V = number of versions of apps)
of trusted servers, which clearly not scalable. MAPREDUCE-2858 only requires
O(1) number of trusted servers.
bq. {quote}It's an operations nightmare to let users to run arbitrary web UI on
a gateway{quote}
bq. 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 .
That's interesting conclusion. The history is showing that we're moving to
webapps, because desktop apps is a nightmare to upgrade/manage/secure :)
bq. 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.
That's because they didn't have any control to the GUI at all in MRv1. MRv2
empowers users to do the who damn thing in a cloud/grid/cluster
efficiently/reliably/securely :)
> 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
