Called when the application ends
Called when the application ends
Called when the application starts
Called when the application starts
Called when a new block manager has joined
Called when a new block manager has joined
Called when an existing block manager has been removed
Called when an existing block manager has been removed
Called when environment properties have been updated
Called when environment properties have been updated
Called when the driver registers a new executor.
Called when the driver registers a new executor.
Called when the driver receives task metrics from an executor in a heartbeat.
Called when the driver receives task metrics from an executor in a heartbeat.
Called when the driver removes an executor.
Called when the driver removes an executor.
Called when a job ends
Called when a job ends
Called when a job starts
Called when a job starts
Called when a stage completes successfully or fails, with information on the completed stage.
Called when a stage completes successfully or fails, with information on the completed stage.
For FIFO, all stages are contained by "default" pool but "default" pool here is meaningless
For FIFO, all stages are contained by "default" pool but "default" pool here is meaningless
Called when a task ends
Called when a task ends
Called when a task begins remotely fetching its result (will not be called for tasks that do not need to fetch the result remotely).
Called when a task begins remotely fetching its result (will not be called for tasks that do not need to fetch the result remotely).
Called when a task starts
Called when a task starts
Called when an RDD is manually unpersisted by the application
Called when an RDD is manually unpersisted by the application
Upon receiving new metrics for a task, updates the per-stage and per-executor-per-stage aggregate metrics by calculating deltas between the currently recorded metrics and the new metrics.
:: DeveloperApi :: Tracks task-level information to be displayed in the UI.
All access to the data structures in this class must be synchronized on the class, since the UI thread and the EventBus loop may otherwise be reading and updating the internal data structures concurrently.