[FLINK-21136] Reactive Mode: Adjust timeout behavior in adaptive scheduler

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available
• Assignee: Robert Metzger
• Reporter: Robert Metzger
• Created: 25/Jan/21 15:37
• Updated: 23/Mar/21 12:48
• Resolved: 23/Mar/21 12:48

Description

The FLIP states the following timeout and resource registration behavior:

On initial startup, the declarative scheduler will wait indefinitely for TaskManagers to show up. Once there are enough TaskManagers available to start the job, and the set of resources is stable (see FLIP-160 for a definition), the job will start running.

Once the job has started running, and a TaskManager is lost, it will wait for 10 seconds for the TaskManager to re-appear. Otherwise, the job will be scheduled again with the available resources. If no TaskManagers are available anymore, the declarative scheduler will wait indefinitely again for new resources.

Issue Links

• links to: GitHub Pull Request #15159