Add a handler for static content.
Add a handler for static content.
Root of where to find resources to serve.
Path in UI where to mount the resources.
Attach a handler to this UI.
Attach a handler to this UI.
Attach a page to this UI.
Attach a page to this UI.
Attach a tab to this UI, along with all of its attached pages.
Attach a tab to this UI, along with all of its attached pages.
Bind to the HTTP server behind this web interface.
Bind to the HTTP server behind this web interface.
Return the actual port to which this server is bound.
Return the actual port to which this server is bound. Only valid after bind().
Detach a handler from this UI.
Detach a handler from this UI.
Returns a list of available applications, in descending order according to their end time.
Returns a list of available applications, in descending order according to their end time.
List of all known applications.
Returns the provider configuration to show in the listing page.
Returns the provider configuration to show in the listing page.
A map with the provider's configuration.
Initialize the history server.
Initialize the history server.
This starts a background thread that periodically synchronizes information displayed on this UI with the event logs in the provided base directory.
Remove a static content handler.
Remove a static content handler.
Path in UI to unmount.
Stop the server and close the file system.
Stop the server and close the file system.
Get the spark UI with the given appID, and apply a function to it.
Get the spark UI with the given appID, and apply a function to it. If there is no such app, throw an appropriate exception
Write the event logs for the given app to the ZipOutputStream instance.
Write the event logs for the given app to the ZipOutputStream instance. If attemptId is None, event logs for all attempts of this application will be written out.
A web server that renders SparkUIs of completed applications.
For the standalone mode, MasterWebUI already achieves this functionality. Thus, the main use case of the HistoryServer is in other deploy modes (e.g. Yarn or Mesos).
The logging directory structure is as follows: Within the given base directory, each application's event logs are maintained in the application's own sub-directory. This is the same structure as maintained in the event log write code path in EventLoggingListener.