Details
-
Umbrella
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0
Description
It's a known fact that the History Server currently has some annoying issues when serving lots of applications, and when serving large applications.
I'm filing this umbrella to track work related to addressing those issues. I'll be attaching a document shortly describing the issues and suggesting a path to how to solve them.
Attachments
Attachments
Issue Links
- Blocked
-
SPARK-21348 Spark history Server load too slow when eventlog is large
- Closed
- blocks
-
SPARK-20656 Incremental parsing of event logs in SHS
- Resolved
- is blocked by
-
SPARK-20205 DAGScheduler posts SparkListenerStageSubmitted before updating stage
- Resolved
-
SPARK-20342 DAGScheduler sends SparkListenerTaskEnd before updating task's accumulators
- Resolved
- is duplicated by
-
SPARK-21348 Spark history Server load too slow when eventlog is large
- Closed
-
SPARK-20582 Speed up the restart of HistoryServer using ApplicationAttemptInfo checkpointing
- Resolved
- is related to
-
SPARK-21254 History UI: Taking over 1 minute for initial page display
- Resolved
-
SPARK-19814 Spark History Server Out Of Memory / Extreme GC
- Closed
-
SPARK-20421 Mark JobProgressListener (and related classes) as deprecated
- Resolved
- relates to
-
SPARK-6951 History server slow startup if the event log directory is large
- Resolved