Are you sure you checked the taskmanager with id
383f6af3299793ba73eeb7bdbab0ddc7? It should log something at the time of
the error, otherwise, this would be very weird.
On Sat, Mar 11, 2017 at 12:01 AM, Govindarajan Srinivasaraghavan <
govindragh...@gmail.com> wrote:
> This is the exception befo
This is the exception before the job went into cancelled state. But when I
looked into the task manager node, the flink process is still running.
java.lang.Exception: TaskManager was lost/killed:
383f6af3299793ba73eeb7bdbab0ddc7 @
ip-xx.xx.xxx.xx.us-west-2.compute.internal (dataPort=37652)
Hi,
this error is only logged at WARN level. As Kaibo already said, its not a
critical issue.
Can you send some more messages from your log. Usually the Jobmanager logs
why a taskmanager has failed. And the last few log messages of the failed
TM itself are also often helpful.
On Fri, Mar 10, 2
I think this is not the root cause of job failure, this task is caused by
other tasks failing. You can check the log of the first failed task.
2017-03-10 12:25 GMT+08:00 Govindarajan Srinivasaraghavan <
govindragh...@gmail.com>:
> Hi All,
>
> I see the below error after running my streaming job f
Hi Subash,
Unfortunately you can not reference a DataStream (loop) within a Flink
operator. To handle both casual and feedback data I suggest using
CoOperators. Have a look at this mockup I did some time ago for a
conceptually similar problem. [1]
[1]
https://github.com/streamline-eu/ML-Pipelines
