Hi,
"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 wrote:
> Javier
> "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
Javier
"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
wrote:
> Hi,
>
> We had the same metaspace problem, it was solved by adding the jar file to
> the /lib path of every ta
Hi,
We had the same metaspace problem, it was solved by adding the jar file to
the /lib path of every task manager, as explained here
https://ci.apache.org/projects/flink/flink-docs-release-1.4/monitoring/debugging_classloading.html#avoiding-dynamic-classloading.
As well we added these java option
I've seen similar problem, but it was not a heap size, but Metaspace.
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
devel
