I got it. That’s really a big problem.
Thank you very much
> On 8 Mar 2018, at 21:03, kedar mhaswade wrote:
>
> Also, in addition to what Gary said, if you take Flink completely out of
> picture and wrote a simple Java class with a main method and the static block
> (!) which does some long r
Also, in addition to what Gary said, if you take Flink completely out of
picture and wrote a simple Java class with a main method and the static
block (!) which does some long running task like getLiveInfo(), then
chances are that your class will make the JVM hang!
Basically what you are doing is
Hi,
You are not shutting down the ScheduledExecutorService [1], which means that
after job cancelation the thread will continue running getLiveInfo(). The
user
code class loader, and your classes won't be garbage collected. You should
use
the RichFunction#close callback to shutdown your thread poo
Hi:
I faced a problem, the taskmanagers in 3 nodes are still running, I make sure
that all job are cancelled, but I could see that stdout logs are still
printing all the way. The job's parallelism is 6.
I wrote a scheduled pool like this
static {
Executors.newScheduledThreadPool(1).schedul