Re: How flink monitor source stream task(Time Trigger) is running?

I think this might not actually be resolved. What YunFan was referring to in the initial mail is the Thread factory that is used for the processing-time service:

Re: How flink monitor source stream task(Time Trigger) is running?

You are welcome :) Piotrek > On Oct 2, 2017, at 1:19 PM, yunfan123 wrote: > > Thank you. > "If SourceFunction.run methods returns without an exception Flink assumes > that it has cleanly shutdown and that there were simply no more elements to > collect/create by

Re: How flink monitor source stream task(Time Trigger) is running?

Thank you. "If SourceFunction.run methods returns without an exception Flink assumes that it has cleanly shutdown and that there were simply no more elements to collect/create by this task. " This sentence solve my confusion. -- Sent from:

Re: How flink monitor source stream task(Time Trigger) is running?

I am still not sure what do you mean by “thread crash without throw”. If SourceFunction.run methods returns without an exception Flink assumes that it has cleanly shutdown and that there were simply no more elements to collect/create by this task. If it continue working, without throwing an

Re: How flink monitor source stream task(Time Trigger) is running?

Any exception thrown by your SourceFunction will be caught by Flink and that will mark a task (that was executing this SourceFuntion) as failed. If you started some custom threads in your SourceFunction, you have to manually propagate their exceptions to the SourceFunction. Piotrek > On Sep

Re: How flink monitor source stream task(Time Trigger) is running?

My source stream means the funciton implement the org.apache.flink.streaming.api.functions.source.SourceFunction. My question is how flink know all working thread is alive? If one working thread that execute the SourceFunction crash, how flink know this happenned? -- Sent from:

Re: How flink monitor source stream task(Time Trigger) is running?

We use Akka's DeathWatch mechanism to detect dead components. TaskManager failure shouldn’t prevent recovering from state (as long as there are enough task slots). I’m not sure if I understand what you mean by "source stream thread" crash. If is was some error during performing a checkpoint so

How flink monitor source stream task(Time Trigger) is running?

In my understanding, flink just use task heartbeat to monitor taskManager is running. If source stream （Time Trigger for XXX）thread is crash, it seems flink can't recovery from this state? -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/