Hi Gary, Yes, my problem mentioned in the original post had been resolved by correcting the zookeeper connection string.
I have two other relevant questions, if you have time, please help: 1. Regarding JM high availability, when I shut down the host having JM running, YARN would detect that missing JM and start a new one after 10 minutes, and the Flink job would be restored. However, on the console screen that I submitted the job, I got the following error messages: "/The program finished with the following exception: org.apache.flink.client.program.ProgramInvocationException/" (full stack trace in the attached file flink_console_timeout.log <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/file/t1586/flink_console_timeout.log> ) Is there any way to avoid this? As if I run this as an AWS EMR job, the job would be considered failed, while it is actually be restored automatically by YARN after 10 minutes). 2. Regarding logging, could you please help explain about the source of the error messages show in "Exception" tab on Flink Job GUI (as per the screenshot below). I could not find any log files has that message (not in jobmanager.log or in taskmanager.log in EMR's hadoop-yarn logs folder). <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/file/t1586/Screen_Shot_2019-01-25_at_22.png> Thanks and regards, Averell -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
