Chesnay Schepler created FLINK-10883: ----------------------------------------
Summary: Submitting a jobs without enough slots times out due to a unspecified timeout Key: FLINK-10883 URL: https://issues.apache.org/jira/browse/FLINK-10883 Project: Flink Issue Type: Improvement Components: Job-Submission Affects Versions: 1.7.0 Reporter: Chesnay Schepler When submitting a job without enough slots being available the job will stay in a SCHEDULED/CREATED state. After some time (a few minutes) the job execution will fail with the following timeout exception: {code} 2018-11-14 13:38:26,615 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph - CHAIN DataSource (at getDefaultTextLineDataSet(WordCountData.java:70) (org.apache.flink.api.java.io.CollectionInputFormat)) -> FlatMap (FlatMap at main(WordCount.java:76)) -> Combine (SUM(1), at main(WordCount.java:79) (1/$java.util.concurrent.TimeoutException at org.apache.flink.runtime.concurrent.FutureUtils$Timeout.run(FutureUtils.java:795) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {code} That the job submission will time out is not documented, neither is which timeout is responsible in the first place or how/whether this can be disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)