Hi everyone, Matthias, Mika and I want to start a discussion about introduction of a new Flink component, the *JobResultStore*.
The main motivation is to address shortcomings of the *RunningJobsRegistry* and surpass it with the new component. These shortcomings have been first described in FLINK-11813 [1]. This change should improve the overall stability of the JobManager's components and address the race conditions in some of the fail over scenarios during the job cleanup lifecycle. It should also help to ensure that Flink doesn't leave any uncleaned resources behind. We've prepared a FLIP-194 [2], which outlines the design and reasoning behind this new component. [1] https://issues.apache.org/jira/browse/FLINK-11813 [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=195726435 We're looking forward for your feedback ;) Best, Matthias, Mika and David
