[SPARK-6951] History server slow startup if the event log directory is large

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 2.4.0
• Component/s: Web UI
• Assignee: Marcelo Masiero Vanzin
• Reporter: Matt Cheah
• Created: 15/Apr/15 22:37
• Updated: 11/Apr/18 14:49
• Resolved: 11/Apr/18 14:49

Description

I started my history server, then navigated to the web UI where I expected to be able to view some completed applications, but the webpage was not available. It turned out that the History Server was not finished parsing all of the event logs in the event log directory that I had specified. I had accumulated a lot of event logs from months of running Spark, so it would have taken a very long time for the History Server to crunch through them all. I purged the event log directory and started from scratch, and the UI loaded immediately.

We should have a pagination strategy or parse the directory lazily to avoid needing to wait after starting the history server.

Issue Links

• is duplicated by: SPARK-9123 Spark HistoryServer load logs too slow and can load the latest logs
• is duplicated by: SPARK-11123 Inprove HistoryServer with multithread to relay logs
• is related to: SPARK-18085 SPIP: Better History Server scalability for many / large applications
• relates to: SPARK-11373 Add metrics to the History Server and providers
• relates to: SPARK-13988 Large history files block new applications from showing up in History UI.
• relates to: SPARK-18010 Remove unneeded heavy work performed by FsHistoryProvider for building up the application listing UI page
• links to: [Github] Pull Request #20952 (vanzin)