flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <rmetz...@apache.org>
Subject Re: HA Mode and standalone containers compatibility ?
Date Thu, 03 Dec 2015 13:03:01 GMT
There is a configuration parameter called "yarn.properties-file.location"
which allows setting a custom path for the properties file.
If the batch and streaming jobs are using different configuration files, it
should work.

On Thu, Dec 3, 2015 at 1:51 PM, Ufuk Celebi <uce@apache.org> wrote:

> I opened an issue for it and it will fixed with the next 0.10.2 release.
>
> @Robert: are you aware of another workaround for the time being?
>
> On Thu, Dec 3, 2015 at 1:20 PM, LINZ, Arnaud <ALINZ@bouyguestelecom.fr>
> wrote:
>
>> Hi,
>> It works fine with that file renamed.  Is there a way to specify its path
>> for a specific execution to have a proper workaround ?
>> Thanks,
>> Arnaud
>>
>> -----Message d'origine-----
>> De : Ufuk Celebi [mailto:uce@apache.org]
>> Envoyé : jeudi 3 décembre 2015 11:53
>> À : user@flink.apache.org
>> Objet : Re: HA Mode and standalone containers compatibility ?
>>
>>
>> > On 03 Dec 2015, at 11:47, LINZ, Arnaud <ALINZ@bouyguestelecom.fr>
>> wrote:
>> >
>> > Oopss... False joy.
>>
>> OK, I think this is a bug in the YARN Client and the way it uses the
>> .properties files to submit jobs.
>>
>> As a work around: Can you mv the /tmp/.yarn-properties-voyager file and
>> submit the batch job?
>>
>> mv /tmp/.yarn-properties-voyager /tmp/.bak.yarn-properties-voyager
>>
>> – Ufuk
>>
>>
>> ________________________________
>>
>> 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.
>>
>
>

Mime
View raw message