Good to hear Cliff.
You're right that it's not a nice user experience. The problem with
queryable state is that one would need to take a look at the actual user
job to decide whether the user uses queryable state or not. But then it's
already too late for starting the respective infrastructure
Hi Till,
Yes, it turns out the problem was
having flink-queryable-state-runtime_2.11-1.6.2.jar in flink/lib. I guess
Queriable State bootstraps itself and, in my situation, it brought the task
manager down when it found no available ports. What's a little troubling is
that I had not configured
Hi Cliff,
the TaskManger fail to start with exit code 31 which indicates an
initialization error on startup. If you check the TaskManager logs via
`yarn logs -applicationId ` you should see the problem why the TMs
don't start up.
Cheers,
Till
On Fri, Nov 9, 2018 at 8:32 PM Cliff Resnick wrote:
Hi Cliff,
this sounds not right. Could you share the logs of the Yarn cluster
entrypoint with the community for further debugging? Ideally on DEBUG
level. The Yarn logs would also be helpful to fully understand the problem.
Thanks a lot!
Cheers,
Till
On Thu, Nov 8, 2018 at 9:59 PM Cliff Resnick
I'm running a YARN cluster of 8 * 4 core instances = 32 cores, with a
configuration of 3 slots per TM. The cluster is dedicated to a single job
that runs at full capacity in "FLIP6" mode. So in this cluster, the
parallelism is 21 (7 TMs * 3, one container dedicated for Job Manager).
When I run
