The option was accepted using the yaml file and it looks likes it solved our
issue.
Thanks again.
From: Robert Metzger [mailto:rmetz...@apache.org]
Sent: mardi 17 novembre 2015 12:04
To: user@flink.apache.org
Subject: Re: MaxPermSize on yarn
You can also put the configuration option into the
incorrectly passed to
> the VM (maybe the “-XX:” causes some issues in the scripts).
>
>
>
> We’ll investigate.
>
>
>
> *From:* Robert Metzger [mailto:rmetz...@apache.org]
> *Sent:* lundi 16 novembre 2015 19:18
> *To:* user@flink.apache.org
> *Subject:* Re: MaxP
exit.
Either is the option is badly supported, or it is incorrectly passed to the VM
(maybe the “-XX:” causes some issues in the scripts).
We’ll investigate.
From: Robert Metzger [mailto:rmetz...@apache.org]
Sent: lundi 16 novembre 2015 19:18
To: user@flink.apache.org
Subject: Re: MaxPermSize on yarn
Hi Gwen,
there is a configuration value called "env.java.opts", that allows you to
pass custom JVM args to JM and TM JVMs.
I hope that helps.
On Mon, Nov 16, 2015 at 5:30 PM, Gwenhael Pasquiers <
gwenhael.pasqui...@ericsson.com> wrote:
> Hi,
>
>
>
> We’re having some OOM permgen exceptions wh
Hi,
We're having some OOM permgen exceptions when running on yarn.
We're not yet sure if it is either a consequence or a cause of our crashes, but
we've been trying to increase that value... And we did not find how to do it.
I've seen that the yarn-daemon.sh sets a 256m value.
It looks to me th
