To verify it just add something after the env.execute() in the wordCount,
like a log or a system out or try to run the program twice and submit it
using the rest API or Web UI.
You'll see that the program will run until the first call to execute, then
nothing else will happen
Hi Mike,
the job seems to run. It might indeed only be a problem with shutting down
the ZooKeeper utils on the client side after the job has been submitted. I
will try to reproduce it locally. Keep us posted on the state of
CURATOR-466 if something should change.
Cheers,
Till
On Thu, Nov 8, 2018
Hi Mike,
could you also send me the YarnJobClusterEntrypoint logs. Thanks!
Cheers,
Till
On Wed, Nov 7, 2018 at 9:27 PM Mikhail Pryakhin wrote:
> Hi Till,
> Thank you for your reply.
> Yes, I’ve upgraded to the latest Flink-1.6.2 and the problem is still
> there, please find the log file attach
Hi Till,Thank you for your reply.Yes, I’ve upgraded to the latest Flink-1.6.2 and the problem is still there, please find the log file attached.
flink-job-1.6.2.log
Description: Binary data
Kind Regards,Mike Pryakhin
On 7 Nov 2018, at 18:46, Till Rohrmann wrote:Hi Mike,ha
Hi Mike,
have you tried whether the problem also occurs with Flink 1.6.2? If yes,
then please share with us the Flink logs with DEBUG log level to further
debug the problem.
Cheers,
Till
On Fri, Oct 26, 2018 at 5:46 PM Mikhail Pryakhin
wrote:
> Hi community!
>
> Righ after I've upgraded flink
Hi community!
Righ after I've upgraded flink up to flink-1.6.1 I get an exception during job
deployment as a YARN cluster.
The job is submitted with zookeper HA enabled, in detached mode.
The flink yaml contains the following properties:
high-availability: zookeeper
high-availability.zookeeper