We will need more information to offer any solution. The exception
simply means that a TaskManager shut down, for which there are a myriad
of possible explanations.
Please have a look at the TaskManager logs, they may contain a hint as
to why it shut down.
On 09.04.2018 16:01, Javier Lopez wrote:
"are you moving the job jar to the ~/flink-1.4.2/lib path ? " ->
Yes, to every node in the cluster.
On 9 April 2018 at 15:37, miki haiat <miko5...@gmail.com
"adding the jar file to the /lib path of every task manager"
are you moving the job jar to the* ~/flink-1.4.2/lib path* ?
On Mon, Apr 9, 2018 at 12:23 PM, Javier Lopez
<javier.lo...@zalando.de <mailto:javier.lo...@zalando.de>> wrote:
We had the same metaspace problem, it was solved by adding the
jar file to the /lib path of every task manager, as explained
As well we added these java options:
From time to time we have the same problem with TaskManagers
disconnecting, but the logs are not useful. We are using 1.3.2.
On 9 April 2018 at 10:41, Alexander Smirnov
I've seen similar problem, but it was not a heap size, but
It was caused by a job restarting in a loop. Looks like
for each restart, Flink loads new instance of classes and
very soon in runs out of metaspace.
I've created a JIRA issue for this problem, but got no
response from the development team on it:
On Mon, Apr 9, 2018 at 11:36 AM 王凯 <wangka...@163.com
thanks a lot,i will try it
在 2018-04-09 00:06:02，"TechnoMage"
I have seen this when my task manager ran out of
RAM. Increase the heap size.
On Apr 8, 2018, at 2:36 AM, 王凯 <wangka...@163.com
hi all, recently, i found a problem,it runs well
when start. But after long run,the exception
display as above,how can resolve it?