Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/10991#issuecomment-177012952
Removing the history serving from Master is pretty straightforward, but
leaves some gaps in the UI and serving JSON requests. I am marking this as WIP
to get some discussion on how to best handle a few of these points.
1. Currently, the Master page has a the application name as a link to the
Application UI Page. While the app is running, it has a link to the live
application server, then when complete the Master replaces that link with one
for the rebuilt UI.
Now, since there is no rebuilt UI, I left the live link, then once complete
the application name is static and does not provide a link
2. Similarly, the Master Application page has a link to "Application
Detail" to open up the Application UI Page. While the app is running, it has a
link to the live application server, then when complete the Master replaces
that link with one for the rebuilt UI.
Now, the live link is still there while the application is running and once
complete the "Application Detail" is removed entirely.
3. Currently, the Master follows the REST API to serve JSON data and the
MasterPage extends the trait `UIRoot` to allow requests for `ApiRootResource`s.
Since a SparkUI with application info is required to serve these resources,
now MasterPage no longer extends this trait.
4. Although the Master can no long serve `ApiRootResource`s, it still can
list applications and also redirect resource requests to any currently running
application.
I put in some functionality that redirects requests, but I stopped short of
serving the application list (the "/applications" endpoint) because it was
getting a little messy. Is this something that is worth having in?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
