[
https://issues.apache.org/jira/browse/SPARK-31196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavol Vidlička updated SPARK-31196:
-----------------------------------
Description:
Loading the list of applications in the History UI does not scale well with a
large number of applications. Fetching and rendering the list for 10k+
applications takes over a minute.
Using `spark.history.ui.maxApplications` is not a great solution, because (as
the name implies), it limits the number of applications shown in the UI, which
hinders usability of the History Server.
A solution would be to use server [side processing of the
DataTable|https://datatables.net/examples/data_sources/server_side]. This would
limit amount of data sent to the client and processed by the browser.
This proposed change plays nicely with KVStore abstraction implemented in
SPARK-18085, which was supposed to solve some of the scalability issues. It
could also definitely solve History UI scalability issues reported for example
in SPARK-21254, SPARK-17243, SPARK-17671
was:
Loading the list of applications in the History UI does not scale well with a
large number of applications. Fetching and rendering the list for 10k+
applications takes over a minute.
Using `spark.history.ui.maxApplications` is not a great solution, because (as
the name implies), it limits the number of applications shown in the UI, which
hinders usability of the History Server.
A solution would be to use server [side processing of the
DataTable|https://datatables.net/examples/data_sources/server_side]. This would
limit amount of data sent to the client and processed by the browser.
This proposed change plays nicely with KVStore abstraction implemented in
SPARK-18085, which was supposed to solve some of the scalability issues.
> Server-side processing of History UI list of applications
> ---------------------------------------------------------
>
> Key: SPARK-31196
> URL: https://issues.apache.org/jira/browse/SPARK-31196
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Affects Versions: 2.3.0
> Reporter: Pavol Vidlička
> Priority: Minor
>
> Loading the list of applications in the History UI does not scale well with a
> large number of applications. Fetching and rendering the list for 10k+
> applications takes over a minute.
> Using `spark.history.ui.maxApplications` is not a great solution, because (as
> the name implies), it limits the number of applications shown in the UI,
> which hinders usability of the History Server.
> A solution would be to use server [side processing of the
> DataTable|https://datatables.net/examples/data_sources/server_side]. This
> would limit amount of data sent to the client and processed by the browser.
> This proposed change plays nicely with KVStore abstraction implemented in
> SPARK-18085, which was supposed to solve some of the scalability issues. It
> could also definitely solve History UI scalability issues reported for
> example in SPARK-21254, SPARK-17243, SPARK-17671
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
