rkhachatryan commented on pull request #12670: URL: https://github.com/apache/flink/pull/12670#issuecomment-645273010
> What about writing a test which starts a checkpoint and then shuts down the CheckpointCoordinator? It can't be triggered deterministically because of concurrency. So we would need to run it in a loop (or decide to make it flaky). But given that it's detected by e2e tests and that `CheckpointCoordinator` threading model is going to be refactored in 1.12 I'm not sure that makes sense. > I think your analysis is not correct. We still have FutureUtils.assertNoException after exceptionally is called. Yes, you are right, it will kill the JVM. The job, however will still be unaffected (same discussion as [above](https://github.com/apache/flink/pull/12670#discussion_r440786956)). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
