Great ;)

Not yet, but you are the second user to request this.
I think I'll put the file somewhere else now.

On Wed, Aug 26, 2015 at 3:19 PM, LINZ, Arnaud <al...@bouyguestelecom.fr>
wrote:

> Ooops… Seems it was rather a write problem on the conf dir…
>
> Sorry, it works!
>
>
>
> BTW, it’s not really nice to have an application write the configuration
> dir ; it’s often a root protected directory in usr/lib/flink. Is there a
> parameter to put that file elsewhere ?
>
>
>
>
>
> *De :* Robert Metzger [mailto:rmetz...@apache.org]
> *Envoyé :* mercredi 26 août 2015 14:42
> *À :* user@flink.apache.org
> *Objet :* Re: [0.10-SNAPSHOT ] When naming yarn application (yarn-session
> -nm), flink run without -m fails.
>
>
>
> Hi Arnaud,
>
>
>
> usually, you don't have to manually specify the JobManager address
> manually with the -m argument, because it is reading it from the
> conf/.yarn-session.properties file.
>
>
>
> Give me a few minutes to reproduce the issue.
>
>
>
> On Wed, Aug 26, 2015 at 2:39 PM, LINZ, Arnaud <al...@bouyguestelecom.fr>
> wrote:
>
> Hi,
> Using last nightly build, it seems that if you call yarn-session.sh with
> -nm option to give a nice application name, then you cannot submit a job
> with flink run without specify the ever changing -m <jobManager> address
> since it does not find it any longer.
>
> Regards,
>
> Arnaud
>
>
> ------------------------------
>
>
> L'intégrité de ce message n'étant pas assurée sur internet, la société
> expéditrice ne peut être tenue responsable de son contenu ni de ses pièces
> jointes. Toute utilisation ou diffusion non autorisée est interdite. Si
> vous n'êtes pas destinataire de ce message, merci de le détruire et
> d'avertir l'expéditeur.
>
> The integrity of this message cannot be guaranteed on the Internet. The
> company that sent this message cannot therefore be held liable for its
> content nor attachments. Any unauthorized use or dissemination is
> prohibited. If you are not the intended recipient of this message, then
> please delete it and notify the sender.
>
>
>

Reply via email to