Re: Task is always created state after submit a example job

I'm glad that you managed to work it out. As far as I understand, without specifying the `taskmanager.host`, Task Manager would try to automatically detect what host/ip address should be advertised to the Job Manager, using which JM can connect to TM. I don't know what is your network setup, what

Re: Task is always created state after submit a example job

There's enough slots on the jobmanger UI, but the slots are not available. After i add taskmanager.host: localhost to flink-conf.yaml, it works. But i don't know why. Thanks, Lei On Fri, Jun 18, 2021 at 6:07 PM Piotr Nowojski wrote: > Hi, > > I would start by looking at the Job Manager and

Re: Task is always created state after submit a example job

Hi, I would start by looking at the Job Manager and Task Manager logs. Take a look if Task Managers connected/registered in the Job Manager and if so, if there were no problems when submitting the job. It seems like either there are not enough slots, or slots are actually not available. Best,

Task is always created state after submit a example job

flink 1.11.2 on a single host. ./bin/start-cluster.sh and then ./bin/flink run examples/streaming/SocketWindowWordCount.jar --hostname localhost --port But on the jobmanager UI, the task is always in created state. There's available slots. Any insights on this? Thanks, Lei