Robert Metzger created FLINK-21136:
--------------------------------------
Summary: Reactive Mode: Adjust timeout behavior in declarative
scheduler
Key: FLINK-21136
URL: https://issues.apache.org/jira/browse/FLINK-21136
Project: Flink
Issue Type: Sub-task
Components: Runtime / Coordination
Reporter: Robert Metzger
Fix For: 1.13.0
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
