Why is it not possible to shut down the local cluster? Can’t you shut it down in the @AfterClass method?
Yes. That will work too. However, then it isn't possible to shut down the local cluster. [Is it necessary to do so or does it shut down automatically when the program exists? I'm not entirely sure.]-- Sachin GoelComputer Science, IIT Delhim. <a href="tel:%2B91-9871457685" value="+919871457685" target="_blank">+91-9871457685On Wed, Sep 2, 2015 at 7:59 PM, Stephan Ewen <[hidden email]> wrote:Have a look at some other tests, like the checkpointing tests. They start one cluster manually and keep it running. They connect against it using the remote environment ("localhost", miniCluster.getJobManagerRpcPort()).That works nicely...On Wed, Sep 2, 2015 at 4:23 PM, Sachin Goel <[hidden email]> wrote:Hi allWhile using LocalEnvironment, in case the program triggers execution several times, the {{LocalFlinkMiniCluster}} is started as many times. This can consume a lot of time in setting up and tearing down the cluster. Further, this hinders with a new functionality I'm working on based on persisted results.One potential solution could be to follow the methodology in `MultipleProgramsTestBase`. The user code then would have to reside in a fixed function name, instead of the main method. Or is that too cumbersome?RegardsSachin-- Sachin GoelComputer Science, IIT Delhim. <a href="tel:%2B91-9871457685" value="+919871457685" target="_blank">+91-9871457685
| Free forum by Nabble | Edit this page |