Hi Arnaud, you can retrieve the logs of a yarn application by calling "yarn logs -applicationId <id>".
Its going to output you the logs of all Taskmanagers and the job manager in one stream. I would pipe the output into a file and then search for the position where the log for the failing taskmanager starts. On Tue, Feb 2, 2016 at 3:15 PM, LINZ, Arnaud <al...@bouyguestelecom.fr> wrote: > Hi, > > Running again with more RAM made the treatement go further, but Yarn still > killed one container for memory consumption. I will experiment various > memory parameters. > > How do I retrieve the log of a specific task manager post-mortem? I don't > use a permanent Flink/Yarn container (it's killed upon batch completion). > > > -----Message d'origine----- > De : Ufuk Celebi [mailto:u...@apache.org] > Envoyé : mardi 2 février 2016 14:41 > This means that the task at task manager bt1shli2/172.21.125.27:49771 > failed during the production of the intermediate data. It’s independent of > the memory problem. > > Could you please check the logs of that task manager? Sorry for the > inconvenience! I hope that we can resolve this shortly. > > – 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. >
