Hi, Thanks for the feedback! As Till explained, the problem is that the JM first tries to schedule the job to the failed TM (which hasn't been detected as failed yet). The configured three restart attempts are "consumed" by these attempts and the job fails afterwards.
Best, Fabian 2018-04-05 8:17 GMT+02:00 dhirajpraj <dhirajp...@gmail.com>: > Just for the record, > It did not work with RestartStrategies.fixedDelayRestart(3, 5000) but > worked > with RestartStrategies.fixedDelayRestart(20, 5000) > > > > -- > Sent from: http://apache-flink-user-mailing-list-archive.2336050. > n4.nabble.com/ >
