Have a look at the class IOManager and IOManagerAsync, it is a good example
of how we use these hooks for cleanup.
The constructor usually installs them, and the shutdown logic removes them.
On Thu, Sep 3, 2015 at 9:19 PM, Stephan Ewen wrote:
> Stopping the JVM process clean up all resources, e
Stopping the JVM process clean up all resources, except temp files.
Everything that creates temp files uses a shutdown hook to remove these:
IOManager, BlobManager, LibraryCache, ...
On Wed, Sep 2, 2015 at 7:40 PM, Sachin Goel
wrote:
> I'm not sure what you mean by "Crucial cleanup is in shutdo
I'm not sure what you mean by "Crucial cleanup is in shutdown hooks". Could
you elaborate?
-- Sachin Goel
Computer Science, IIT Delhi
m. +91-9871457685
On Wed, Sep 2, 2015 at 10:25 PM, Stephan Ewen wrote:
> You can always shut down a cluster manually (via shutdown()) and if the
> JVM simply exi
You can always shut down a cluster manually (via shutdown()) and if the JVM
simply exists, all is well as well. Crucial cleanup is in shutdown hooks.
On Wed, Sep 2, 2015 at 6:22 PM, Till Rohrmann
wrote:
> If I'm not mistaken, then the cluster should be properly terminated when
> it gets garbage
If I'm not mistaken, then the cluster should be properly terminated when it
gets garbage collected. Thus, also when the main method exits.
On Wed, Sep 2, 2015 at 6:14 PM, Sachin Goel
wrote:
> If I'm right, all Tests use either the MultipleProgramTestBase or
> JavaProgramTestBase. Those shut dow
If I'm right, all Tests use either the MultipleProgramTestBase or
JavaProgramTestBase. Those shut down the cluster explicitly anyway.
I will make sure if this is the case.
Regards
Sachin
-- Sachin Goel
Computer Science, IIT Delhi
m. +91-9871457685
On Wed, Sep 2, 2015 at 9:40 PM, Till Rohrmann
Okay. No problem.
Any suggestions for the correct context though? :')
I don't think something like a {{FlinkProgram}} class is a good idea [User
would need to override a {{program}} method and we will make sure the
cluster is setup only once and torn down properly only after the user code
finishes
Maybe we can create a single PlanExecutor for the LocalEnvironment which is
used when calling execute. This of course entails that we don’t call stop
on the LocalCluster. For cases where the program exits after calling
execute, this should be fine because all resources will then be released
anyway.
Oh sorry, then I got the wrong context. I somehow thought it was about test
cases because I read `MultipleProgramTestBase` etc. Sorry my bad.
On Wed, Sep 2, 2015 at 6:00 PM, Sachin Goel
wrote:
> I was under the impression that the @AfterClass annotation can only be
> used in test classes.
> Even
I was under the impression that the @AfterClass annotation can only be used
in test classes.
Even so, the idea is that a user program running in the IDE should not be
starting up the cluster several times [my primary concern is the addition
of the persist operator], and we certainly cannot ask the
Why is it not possible to shut down the local cluster? Can’t you shut it
down in the @AfterClass method?
On Wed, Sep 2, 2015 at 4:56 PM, Sachin Goel
wrote:
> 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 dow
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 Goel
Computer Science, IIT Delhi
m. +91-9871457685
On Wed, Sep 2, 2015 at 7:59 PM, Steph
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
wrote:
> H
13 matches
Mail list logo
