[FLINK-10644] Batch Job: Speculative execution

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Component/s: Runtime / Coordination
• Labels: stale-assigned
• Assignee: BoWang
• Reporter: JIN SUN
• Created: 22/Oct/18 23:44
• Updated: 20/Jun/22 11:27
• Resolved: 19/Apr/21 08:12

Description

Strugglers/outlier are tasks that run slower than most of the all tasks in a Batch Job, this somehow impact job latency, as pretty much this straggler will be in the critical path of the job and become as the bottleneck.

Tasks may be slow for various reasons, including hardware degradation, or software mis-configuration, or noise neighboring. It's hard for JM to predict the runtime.

To reduce the overhead of strugglers, other system such as Hadoop/Tez, Spark has speculative execution. Speculative execution is a health-check procedure that checks for tasks to be speculated, i.e. running slower in a ExecutionJobVertex than the median of all successfully completed tasks in that EJV, Such slow tasks will be re-submitted to another TM. It will not stop the slow tasks, but run a new copy in parallel. And will kill the others if one of them complete.

This JIRA is an umbrella to apply this kind of idea in FLINK. Details will be append later.

Issue Links

• relates to: FLINK-28131 FLIP-168: Speculative Execution for Batch Job

Sub-Tasks

• Make SpillableSubpartition repeatably read to enable: Closed
• Report more record information in IOMetrics for Speculative Schedule: Closed
• Distinguish long tail task based on IOMetrics: Closed
• Speculatively schedule execution for long tail task: Closed